From: Daniel Borkmann <daniel-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: ast-uqk4Ao+rVK5Wk0Htik3J/w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH man v2] bpf.2: various updates/follow-ups to address some fixmes
Date: Tue, 28 Jul 2015 22:57:59 +0200 [thread overview]
Message-ID: <55B7ECD7.4020103@iogearbox.net> (raw)
In-Reply-To: <55B7E57E.9090401-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org>
On 07/28/2015 10:26 PM, Daniel Borkmann wrote:
> On 07/28/2015 09:48 PM, Michael Kerrisk (man-pages) wrote:
>> Hi Daniel,
>>
>> On 07/28/2015 08:59 PM, Daniel Borkmann wrote:
>>> A couple of follow-ups to the bpf(2) man-page.
>>
>> Could you write a short change log summarizing the changes
>> made by the patch, please :-).
>>
>> Nice work, but I have some comments below. Would you be so kind as to
>> send a v3?
>
> Ok, done. I think I've addressed all your feedback.
Couple of more follow-ups will come later on to address program
types, etc.
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-28 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 18:59 [PATCH man v2] bpf.2: various updates/follow-ups to address some fixmes Daniel Borkmann
[not found] ` <36d5ffdcb1dc318cb25e0785eba31aff3014772f.1438109790.git.daniel-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org>
2015-07-28 19:01 ` Alexei Starovoitov
2015-07-28 19:48 ` Michael Kerrisk (man-pages)
[not found] ` <55B7DC72.40205-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-07-28 20:26 ` Daniel Borkmann
[not found] ` <55B7E57E.9090401-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org>
2015-07-28 20:57 ` 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=55B7ECD7.4020103@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 \
/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).