[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180813193738.od5k2wwc7dtrxyqp@ast-mbp>
Date: Mon, 13 Aug 2018 12:37:40 -0700
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: "Tobin C. Harding" <me@...in.cc>
Cc: Jonathan Corbet <corbet@....net>,
Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <ast@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Kees Cook <keescook@...omium.org>,
Andy Lutomirski <luto@...capital.net>,
Will Drewry <wad@...omium.org>, linux-doc@...r.kernel.org,
Network Development <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH bpf-next 0/4] Convert filter.txt to RST
On Sat, Aug 11, 2018 at 09:50:58PM +1000, Tobin C. Harding wrote:
> On Fri, Aug 10, 2018 at 10:51:28AM -0700, Alexei Starovoitov wrote:
> > On Fri, Aug 10, 2018 at 5:57 AM Jonathan Corbet <corbet@....net> wrote:
> > >
> > > The objective actually is to have SPDX tags in all files in the kernel.
> > > That includes documentation, even though people, as always, care less
> > > about the docs than they do the code.
> >
> > right, but let's do that as a separate patch set.
> > In the current set I'd focus on reviewing the actual doc changes.
> > In particular completely removing
> > Documentation/networking/filter.txt
> > feels wrong, since lots of websites point directly there.
> > Can we have at least few words there pointing to new location?
>
> Something like ...
>
>
> ------------ filter.txt
>
> BPF documentation can now be found in the following places:
>
> - Introduction to BPF (Linux Socket Filter) - Documentation/userspace-api/socket-filter.rst
> - Classic BPF (cBPF) - Documentation/userspace-api/cBPF.rst
> - Internal BPF (eBPF) - Documentation/userspace-api/eBPF.rst
Internal ?
that was the name we used for may be a month many years ago.
Please use 'extended BPF' in new filter.txt and all other places.
since merge window is open the patches would need to wait until
bpf-next opens up in few weeks.
Thanks
Powered by blists - more mailing lists