From: Daniel Borkmann <daniel-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org>
To: vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
ast-uqk4Ao+rVK5Wk0Htik3J/w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH man v3] bpf.2: various updates/follow-ups to address some fixmes
Date: Wed, 29 Jul 2015 09:27:30 +0200 [thread overview]
Message-ID: <55B88062.6090505@iogearbox.net> (raw)
In-Reply-To: <20150729055811.GH21252@vapier>
On 07/29/2015 07:58 AM, Mike Frysinger wrote:
> On 28 Jul 2015 22:25, Daniel Borkmann wrote:
>> -.BR bpf ()
>> +.BR bpf (2)
>
> i thought the style for man pages was to not include the section number for the
> function you're currently documenting. since this is already the bpf(2) page,
> it should use "bpf()" and not "bpf(2)". other man pages though should use
> "bpf(2)".
Ok, I was not aware of that. This accounts for the entire man page?
There are a couple of other spots using bpf(2), so I would fix them as well in v4.
Thanks,
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-07-29 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 20:25 [PATCH man v3] bpf.2: various updates/follow-ups to address some fixmes Daniel Borkmann
[not found] ` <86038f69cd3d753350b9947b675365fb7fe9da60.1438114491.git.daniel-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org>
2015-07-29 5:58 ` Mike Frysinger
2015-07-29 7:27 ` Daniel Borkmann [this message]
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=55B88062.6090505@iogearbox.net \
--to=daniel-fec+5ew28dpmcu3hniyyjq@public.gmane.org \
--cc=ast-uqk4Ao+rVK5Wk0Htik3J/w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.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).