From: Felix Janda <felix.janda@posteo.de>
To: libtirpc-devel@lists.sourceforge.net
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 3/7] svc_raw.c: Include <string.h> for memset
Date: Sun, 17 Apr 2016 11:10:23 +0200 [thread overview]
Message-ID: <20160417091023.GC2737@nyan> (raw)
Signed-off-by: Felix Janda <felix.janda@posteo.de>
---
src/svc_raw.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/svc_raw.c b/src/svc_raw.c
index a8a396f..0eb0965 100644
--- a/src/svc_raw.c
+++ b/src/svc_raw.c
@@ -43,6 +43,7 @@
#include <sys/types.h>
#include <rpc/raw.h>
#include <stdlib.h>
+#include <string.h>
#ifndef UDPMSGSIZE
#define UDPMSGSIZE 8800
--
2.7.3
reply other threads:[~2016-04-17 9:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160417091023.GC2737@nyan \
--to=felix.janda@posteo.de \
--cc=libtirpc-devel@lists.sourceforge.net \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).