From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesper Dangaard Brouer Subject: Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter Date: Tue, 7 Feb 2017 17:09:08 +0100 Message-ID: <20170207170908.492d71c0@redhat.com> References: <148647756092.10567.10947541548678801938.stgit@localhost> <20170207083717.1c98f608@lwn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org, Alexei Starovoitov , alexander@alemayhu.com, linux-kernel@vger.kernel.org, quentin.monnet@6wind.com, Daniel Borkmann , brouer@redhat.com To: Jonathan Corbet Return-path: In-Reply-To: <20170207083717.1c98f608@lwn.net> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Tue, 7 Feb 2017 08:37:17 -0700 Jonathan Corbet wrote: > On Tue, 07 Feb 2017 15:30:11 +0100 > Jesper Dangaard Brouer 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