From: Daniel Borkmann <daniel@iogearbox.net>
To: "Tobin C. Harding" <me@tobin.cc>, Alexei Starovoitov <ast@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
"David S. Miller" <davem@davemloft.net>,
Jay Schulist <jschlst@samba.org>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC bpf-next 3/3] docs: Split filter.txt into separate documents.
Date: Thu, 2 Aug 2018 10:02:50 +0200 [thread overview]
Message-ID: <514b4a99-5ebd-9bb5-f6f3-99fe1b19c25d@iogearbox.net> (raw)
In-Reply-To: <20180802062848.14332-4-me@tobin.cc>
On 08/02/2018 08:28 AM, Tobin C. Harding wrote:
> In preparation for conversion of Documentation/networking/filter.txt it was
> noticed that the document contains a lot of information. The document may be
> more accessible if it was split up. Some parts pertain to everyone, let's put
> these bits in core-api/. The more hard core bits about eBPF internals could be
> put with the other BPF docs in Documentation/bpf/. There is a small bit of
> information on testing and miscellaneous matters that are useful for everyone
> (everyone does testing, right) so lets keep that info at the bottom of both new
> documents. (This includes the original authors.)
>
> Split Documentation/networking/filter.txt into Documentation/bpf/eBPF.rst and
> Documentation/core-api/bpf.rst
>
> Cc: Jay Schulist <jschlst@samba.org>
> Cc: Daniel Borkmann <daniel@iogearbox.net>
> Cc; Alexei Starovoitov <ast@kernel.org>
> Signed-off-by: Tobin C. Harding <me@tobin.cc>
> ---
> Documentation/networking/filter.txt | 1480 ---------------------------
> 1 file changed, 1480 deletions(-)
> delete mode 100644 Documentation/networking/filter.txt
Missing git add given the new files are not present here?
Overall I agree it would be good if we move all the content over into
Documentation/bpf/ eventually, but would be useful to see a full diff.
next prev parent reply other threads:[~2018-08-02 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 6:28 [RFC bpf-next 0/3] docs: Convert filter.txt to RST Tobin C. Harding
2018-08-02 6:28 ` [RFC bpf-next 1/3] docs: net: Fix various minor typos Tobin C. Harding
2018-08-02 6:28 ` [RFC bpf-next 2/3] docs: net: Use lowercase 'k' for kernel Tobin C. Harding
2018-08-02 6:28 ` [RFC bpf-next 3/3] docs: Split filter.txt into separate documents Tobin C. Harding
2018-08-02 8:02 ` Daniel Borkmann [this message]
2018-08-02 11:03 ` Tobin C. Harding
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=514b4a99-5ebd-9bb5-f6f3-99fe1b19c25d@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=jschlst@samba.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@tobin.cc \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®