From: Christoph Hellwig <hch@lst.de>
To: Daniel Borkmann <daniel@iogearbox.net>
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>,
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 1/2] bpf, docs: prune all references to "internal BPF"
Date: Fri, 19 Nov 2021 07:15:28 +0100 [thread overview]
Message-ID: <20211119061528.GA15129@lst.de> (raw)
In-Reply-To: <1bb1c024-55a0-b9bf-8aa1-2bfd7a3c367d@iogearbox.net>
On Thu, Nov 18, 2021 at 12:09:02AM +0100, Daniel Borkmann wrote:
> Thanks for the cleanup! For the code occurrences with 'internal BPF', I would
> just drop the term 'internal' so it's only 'BPF' which is consistent with the
> rest in the kernel. Usually eBPF is implied given all the old cBPF stuff is
> translated to it anyway. Bit confusing, but that's where it converged over the
> years in the kernel including git log. eBPF vs cBPF unless it's explicitly
> intended to be called out (like in the filter.rst docs).
Ok.
> nit: We can probably just drop that comment since it's not very useful anyway
> and already implied by the function name.
Sounds good.
next prev parent reply other threads:[~2021-11-19 6:15 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 [this message]
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
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=20211119061528.GA15129@lst.de \
--to=hch@lst.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.