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.

client, event_pipe: explicitly ignore the write() result
8ce2ec7a · Max Kellermann · a96bec36 · 8ce2ec7a · 8ce2ec7a
Commit 8ce2ec7a authored Apr 01, 2009 by Max Kellermann
Hide whitespace changes
Inline Side-by-side

Showing with 2 additions and 2 deletions

client.c src/client.c +1 -1

event_pipe.c src/event_pipe.c +1 -1

No files found.
--- 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)

--- 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);
 }