From: Christoph Hellwig <hch@lst.de>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>, Jonathan Corbet <corbet@lwn.net>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH 2/2] bpf, doc: split general purpose eBPF documentation out of filter.rst
Date: Fri, 19 Nov 2021 07:16:42 +0100 [thread overview]
Message-ID: <20211119061642.GB15129@lst.de> (raw)
In-Reply-To: <20211118005613.g4sqaq2ucgykqk2m@ast-mbp>
On Wed, Nov 17, 2021 at 04:56:13PM -0800, Alexei Starovoitov wrote:
> I think the split would be good in the long term, but please make the links
> more obvious somehow in the filter.rst, since a bunch of posts on the web
> link back to that file. The folks who will be reading the revamped filter.rst
> would need a very obvious way to navigate to new pages.
What would be a good way to make it more obvious? Add a section with
links to the three new documentents and/or the Documentation/bpf/
index?
> In terms of followups and cleanup... please share what you have in mind.
The prime issue I'd like to look in is to replace all the references
to classic BPF and instead make the document standadlone.
next prev parent reply other threads:[~2021-11-19 6:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 13:07 split up filter.rst Christoph Hellwig
2021-11-15 13:07 ` [PATCH 1/2] bpf, docs: prune all references to "internal BPF" Christoph Hellwig
2021-11-17 23:09 ` Daniel Borkmann
2021-11-19 6:15 ` Christoph Hellwig
2021-11-15 13:07 ` [PATCH 2/2] bpf, doc: split general purpose eBPF documentation out of filter.rst Christoph Hellwig
2021-11-18 0:56 ` Alexei Starovoitov
2021-11-19 6:16 ` Christoph Hellwig [this message]
2021-11-19 13:03 ` Toke Høiland-Jørgensen
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=20211119061642.GB15129@lst.de \
--to=hch@lst.de \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/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).