Browse Source

daemon_conn: don't expose daemon_conn_write_next.

No external callers.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
plugin-1
Rusty Russell 6 years ago
parent
commit
88da956531
  1. 4
      common/daemon_conn.c
  2. 9
      common/daemon_conn.h

4
common/daemon_conn.c

@ -13,8 +13,8 @@ struct io_plan *daemon_conn_read_next(struct io_conn *conn,
dc);
}
struct io_plan *daemon_conn_write_next(struct io_conn *conn,
struct daemon_conn *dc)
static struct io_plan *daemon_conn_write_next(struct io_conn *conn,
struct daemon_conn *dc)
{
const u8 *msg;

9
common/daemon_conn.h

@ -65,15 +65,6 @@ void daemon_conn_wake(struct daemon_conn *dc);
*/
void daemon_conn_send_fd(struct daemon_conn *dc, int fd);
/**
* daemon_conn_write_next - Continue writing from the msg-queue
*
* Exposed here so that, if `msg_queue_cleared_cb` is used to break
* out of the write-loop, we can get back in.
*/
struct io_plan *daemon_conn_write_next(struct io_conn *conn,
struct daemon_conn *dc);
/**
* daemon_conn_read_next - Read the next message
*/

Loading…
Cancel
Save