From: David Gibson <david@gibson.dropbear.id.au>
To: andrew@aj.id.au
Cc: ccan@lists.ozlabs.org
Subject: [PATCH] strgrp: Fix compile errors in example
Date: Mon, 14 Sep 2015 21:25:19 +1000 [thread overview]
Message-ID: <1442229919-5163-1-git-send-email-david@gibson.dropbear.id.au> (raw)
Commit 63f13d6 "strgrp: Tidy up kerneldoc in _info" introduced some compile
errors into the example in strgrp/_info. This fixes them.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
ccan/strgrp/_info | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
I've just committed this fix for errors in the strgrp _info file.
This one got caught by the Travis CI system, which I wired ccan up to
a little while back - see
https://travis-ci.org/rustyrussell/ccan/builds.
It seems to work pretty well, so I highly recommend it. If you have a
github tree, it's trivial to wire up (e.g. mine's at
https://travis-ci.org/dgibson/ccan).
diff --git a/ccan/strgrp/_info b/ccan/strgrp/_info
index 98f9bb2..e0b70b4 100644
--- a/ccan/strgrp/_info
+++ b/ccan/strgrp/_info
@@ -56,7 +56,7 @@
* Author: Andrew Jeffery <andrew@aj.id.au>
*
* Example:
- * FILE *const f;
+ * FILE *f;
* char *buf;
* struct strgrp *ctx;
* struct strgrp_iter *iter;
@@ -77,10 +77,10 @@
*
* // Re-implement something similar to strgrp_print() via API as an
* // example
- * *iter = strgrp_iter_new(ctx);
+ * iter = strgrp_iter_new(ctx);
* while(NULL != (grp = strgrp_iter_next(iter))) {
* printf("%s\n", strgrp_grp_key(grp));
- * *grp_iter = strgrp_grp_iter_new(grp);
+ * grp_iter = strgrp_grp_iter_new(grp);
* while(NULL != (item = strgrp_grp_iter_next(grp_iter))) {
* printf("\t%s\n", strgrp_item_key(item));
* }
--
2.4.3
_______________________________________________
ccan mailing list
ccan@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/ccan
next reply other threads:[~2015-09-14 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 11:25 David Gibson [this message]
2015-09-14 12:14 ` [PATCH] strgrp: Fix compile errors in example Andrew Jeffery
2015-09-14 23:55 ` David Gibson
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=1442229919-5163-1-git-send-email-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=andrew@aj.id.au \
--cc=ccan@lists.ozlabs.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).