From: Alexei Starovoitov <ast-uqk4Ao+rVK5Wk0Htik3J/w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: Daniel Borkmann <daniel-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org>,
lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: ebpf(2) man page
Date: Mon, 09 Mar 2015 10:28:21 -0700 [thread overview]
Message-ID: <54FDD835.60605@plumgrid.com> (raw)
In-Reply-To: <CAKgNAki-qkJzuuq=dXMJnE2sqjeViLeG7-yjvP7kTcShMX7hrA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 3/9/15 7:18 AM, Michael Kerrisk (man-pages) wrote:
> Hello Alexei
>
> A while ago you posted a man page text for ebpf(2) at
> http://lwn.net/Articles/613387/
> I have taken a while to catch up, but will aim to get that into
> man-pages at some point in the not too distant future.
>
> Is the text at that link the latest version?
>
> Also, is you text just a plain text file, or is there a man source
> mark up file? If the latter exists, could you send it?
Thanks for the ping.
My excuse for not sending official man-pages.git patch yet is that
I was hoping to land bpf+tracing bits and talk about both tracing
and networking use cases in the man page.
I guess it's ok to update it incrementally. Will send it soon.
--
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-03-09 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 14:18 ebpf(2) man page Michael Kerrisk (man-pages)
[not found] ` <CAKgNAki-qkJzuuq=dXMJnE2sqjeViLeG7-yjvP7kTcShMX7hrA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-09 17:28 ` Alexei Starovoitov [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=54FDD835.60605@plumgrid.com \
--to=ast-uqk4ao+rvk5wk0htik3j/w@public.gmane.org \
--cc=daniel-FeC+5ew28dpmcu3hnIyYJQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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).