From 8ce2ec7aedf995a37953711e0866a9beef0ae243 Mon Sep 17 00:00:00 2001 From: Max Kellermann Date: Wed, 1 Apr 2009 17:14:25 +0200 Subject: client, event_pipe: explicitly ignore the write() result On both locations, the result of write() can be ignored safely. In event_pipe_emit_fast(), that can only be "EAGAIN", which means that the pipe buffer is full - no further notification required. In client_init(), that would be a fatal connection error, which would be caught by the next event. This patch fixes gcc warnings. --- src/client.c | 2 +- src/event_pipe.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/client.c b/src/client.c index bb204412..3c5ec566 100644 --- a/src/client.c +++ b/src/client.c @@ -205,7 +205,7 @@ static void client_init(struct client *client, int fd) client->permission = getDefaultPermissions(); - write(fd, GREETING, sizeof(GREETING) - 1); + (void)write(fd, GREETING, sizeof(GREETING) - 1); } static void free_cmd_list(GSList *list) diff --git a/src/event_pipe.c b/src/event_pipe.c index 6eddd0b1..3e500915 100644 --- a/src/event_pipe.c +++ b/src/event_pipe.c @@ -149,5 +149,5 @@ void event_pipe_emit_fast(enum pipe_event event) assert((unsigned)event < PIPE_EVENT_MAX); pipe_events[event] = true; - write(event_pipe[1], "", 1); + (void)write(event_pipe[1], "", 1); } -- cgit v1.2.3