From: Pete Zaitcev <zaitcev@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: [Patch 3/3] chunkd: add include w/prototypes
Date: Tue, 30 Mar 2010 20:58:16 -0600 [thread overview]
Message-ID: <20100330205816.21935cb0@redhat.com> (raw)
Caught by gcc: the prototypes are not in the header that we expected.
Signed-off-by: Pete Zaitcev <zaitcev@redhat.com>
---
lib/chunksrv.c | 1 +
1 file changed, 1 insertion(+)
diff -urp -X dontdiff chunkd-m/lib/chunksrv.c chunkd-tip/lib/chunksrv.c
--- chunkd-m/lib/chunksrv.c 2010-03-30 15:08:36.000000000 -0600
+++ chunkd-tip/lib/chunksrv.c 2010-03-23 18:55:46.000000000 -0600
@@ -24,6 +24,7 @@
#include <openssl/hmac.h>
#include <glib.h>
#include <chunk_msg.h>
+#include <chunksrv.h> /* req_len, chreq_sign proto */
size_t req_len(const struct chunksrv_req *req)
{
diff -urp -X dontdiff chunkd-m/server/cldu.c chunkd-tip/server/cldu.c
reply other threads:[~2010-03-31 2:58 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=20100330205816.21935cb0@redhat.com \
--to=zaitcev@redhat.com \
--cc=hail-devel@vger.kernel.org \
--cc=jeff@garzik.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 read-only IMAP folder(s) and NNTP newsgroup(s).