From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org,
Alexei Starovoitov <ast@fb.com>,
alexander@alemayhu.com, linux-kernel@vger.kernel.org,
quentin.monnet@6wind.com,
Daniel Borkmann <borkmann@iogearbox.net>,
brouer@redhat.com
Subject: Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter
Date: Tue, 7 Feb 2017 17:09:08 +0100 [thread overview]
Message-ID: <20170207170908.492d71c0@redhat.com> (raw)
In-Reply-To: <20170207083717.1c98f608@lwn.net>
On Tue, 7 Feb 2017 08:37:17 -0700
Jonathan Corbet <corbet@lwn.net> wrote:
> On Tue, 07 Feb 2017 15:30:11 +0100
> Jesper Dangaard Brouer <brouer@redhat.com> wrote:
>
> > Question: What kernel tree should this go into???
> >
> > If going through Jonathan Corbet, will it appear sooner here???
> > https://www.kernel.org/doc/html/latest/
What about this question? Or let me ask in another way, what tree is
https://www.kernel.org/doc/html/latest/ based on?
> > If it will not appear sooner that way, then it's likely best to keep
> > it in sync with the tree that takes eBPF code changes.
>
> I've developed a fairly strong preference for carrying patches touching
> index.rst; otherwise I spend a lot of time explaining merge conflicts to
> Linus.
>
> If the consensus is that this is ready to go, I expect I can squeeze it in
> for 4.11. I'm not too worried about regressions...:)
>
> I haven't actually built it yet, but from a first look it seems like an
> awfully good start. The one thing that comes to mind is that I'm likely
> to want to move it at some point. I'd really like to start a separate
> book for user-space developer documentation, and this would certainly
> belong there. That book doesn't exist yet, though, so I can't quite blame
> you, hard as I might try, for not putting this document there.
Yes, I was also wondering hard where to put it... and a book for
user-space developer documentation would likely be the right place, but
it was not there, as you mention ;-)
I'm fine with moving it later under another "book". Linking to it as
HTML would still be the same right? (https://www.kernel.org/doc/html/latest/bpf/index.html)
And is the Documentation/bpf/ directory the correct place?
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2017-02-07 16:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 14:30 [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter Jesper Dangaard Brouer
2017-02-07 14:30 ` [net-next PATCH 1/4] doc/bpf: start eBPF documentation tree bpf/ Jesper Dangaard Brouer
2017-02-07 14:30 ` [net-next PATCH 2/4] doc/bpf: document interacting with eBPF maps Jesper Dangaard Brouer
2017-02-07 14:30 ` [net-next PATCH 3/4] doc/bpf: describes the different types of eBPF maps available Jesper Dangaard Brouer
2017-02-07 14:30 ` [net-next PATCH 4/4] doc/bpf: describe BCC the BPF Compiler Collection Jesper Dangaard Brouer
2017-02-07 15:37 ` [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter Jonathan Corbet
2017-02-07 16:09 ` Jesper Dangaard Brouer [this message]
2017-02-07 16:46 ` Jonathan Corbet
2017-02-07 20:51 ` Jesper Dangaard Brouer
2017-02-07 21:23 ` Jonathan Corbet
2017-02-08 10:36 ` Jesper Dangaard Brouer
2017-02-07 16:43 ` Daniel Borkmann
2017-02-07 21:19 ` Jesper Dangaard Brouer
2017-02-07 22:32 ` Daniel Borkmann
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=20170207170908.492d71c0@redhat.com \
--to=brouer@redhat.com \
--cc=alexander@alemayhu.com \
--cc=ast@fb.com \
--cc=borkmann@iogearbox.net \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=quentin.monnet@6wind.com \
/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).