Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1575833
| From | Jesper Dangaard Brouer <brouer@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter |
| Date | 2017-02-07 17:20 +0100 |
| Message-ID | <t8gEN-5ar-9@gated-at.bofh.it> (permalink) |
| References | <t8f62-45q-9@gated-at.bofh.it> <t8g25-4G5-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter Jesper Dangaard Brouer <brouer@redhat.com> - 2017-02-07 15:40 +0100
[net-next PATCH 1/4] doc/bpf: start eBPF documentation tree bpf/ Jesper Dangaard Brouer <brouer@redhat.com> - 2017-02-07 15:40 +0100
Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter Jonathan Corbet <corbet@lwn.net> - 2017-02-07 16:40 +0100
Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter Jesper Dangaard Brouer <brouer@redhat.com> - 2017-02-07 17:20 +0100
Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter Jonathan Corbet <corbet@lwn.net> - 2017-02-07 17:50 +0100
Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter Jesper Dangaard Brouer <brouer@redhat.com> - 2017-02-07 22:00 +0100
Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter Jonathan Corbet <corbet@lwn.net> - 2017-02-07 22:40 +0100
Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter Jesper Dangaard Brouer <brouer@redhat.com> - 2017-02-08 11:40 +0100
Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter Daniel Borkmann <daniel@iogearbox.net> - 2017-02-07 17:50 +0100
Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter Jesper Dangaard Brouer <brouer@redhat.com> - 2017-02-07 22:30 +0100
Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter Daniel Borkmann <daniel@iogearbox.net> - 2017-02-07 23:40 +0100
csiph-web