From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Tobin C. Harding" <me@tobin.cc>,
Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Kees Cook <keescook@chromium.org>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
linux-doc@vger.kernel.org,
Network Development <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf-next 0/4] Convert filter.txt to RST
Date: Fri, 10 Aug 2018 10:51:28 -0700 [thread overview]
Message-ID: <CAADnVQL-ekJXQoP+Peuh1uBJ1RGxMJ0G0DVp-UoGcWOY9BATeQ@mail.gmail.com> (raw)
In-Reply-To: <20180810065752.2ab5473d@lwn.net>
On Fri, Aug 10, 2018 at 5:57 AM Jonathan Corbet <corbet@lwn.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?
next prev parent reply other threads:[~2018-08-10 17:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 5:23 [PATCH bpf-next 0/4] Convert filter.txt to RST Tobin C. Harding
2018-08-09 5:23 ` [PATCH bpf-next 1/4] docs: net: Fix various minor typos Tobin C. Harding
2018-08-09 5:23 ` [PATCH bpf-next 2/4] docs: Separate and convert filter.txt to RST Tobin C. Harding
2018-08-09 5:23 ` [PATCH bpf-next 3/4] docs: Judiciously use double ticks Tobin C. Harding
2018-08-09 5:23 ` [PATCH bpf-next 4/4] docs: Remove filter.txt from the tree Tobin C. Harding
2018-08-09 6:07 ` [PATCH bpf-next 0/4] Convert filter.txt to RST Alexei Starovoitov
2018-08-09 7:27 ` Tobin C. Harding
2018-08-09 8:24 ` Daniel Borkmann
2018-08-10 1:46 ` Tobin C. Harding
2018-08-10 12:57 ` Jonathan Corbet
2018-08-10 17:51 ` Alexei Starovoitov [this message]
2018-08-11 11:50 ` Tobin C. Harding
2018-08-13 19:37 ` Alexei Starovoitov
2018-08-10 21:54 ` 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=CAADnVQL-ekJXQoP+Peuh1uBJ1RGxMJ0G0DVp-UoGcWOY9BATeQ@mail.gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=me@tobin.cc \
--cc=netdev@vger.kernel.org \
--cc=wad@chromium.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;
as well as URLs for NNTP newsgroup(s).