From: David Vernet <void@manifault.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Andrii Nakryiko <andrii@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
bpf@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 04/35] Documentation: bpf: correct spelling
Date: Mon, 30 Jan 2023 08:26:59 -0600 [thread overview]
Message-ID: <Y9fTs88hb84+TFLn@maniforge> (raw)
In-Reply-To: <Y9fTJLNVc5i2/XV5@maniforge>
On Mon, Jan 30, 2023 at 08:24:36AM -0600, David Vernet wrote:
> On Thu, Jan 26, 2023 at 10:39:34PM -0800, Randy Dunlap wrote:
> > Correct spelling problems for Documentation/bpf/ as reported
> > by codespell.
> >
> > Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> > Cc: Andrii Nakryiko <andrii@kernel.org>
> > Cc: Alexei Starovoitov <ast@kernel.org>
> > Cc: Daniel Borkmann <daniel@iogearbox.net>
> > Cc: bpf@vger.kernel.org
> > Cc: Jonathan Corbet <corbet@lwn.net>
> > Cc: linux-doc@vger.kernel.org
> > ---
> > Documentation/bpf/libbpf/libbpf_naming_convention.rst | 6 +++---
> > Documentation/bpf/map_xskmap.rst | 2 +-
> > Documentation/bpf/ringbuf.rst | 4 ++--
> > Documentation/bpf/verifier.rst | 2 +-
> > 4 files changed, 7 insertions(+), 7 deletions(-)
> >
> > diff -- a/Documentation/bpf/libbpf/libbpf_naming_convention.rst b/Documentation/bpf/libbpf/libbpf_naming_convention.rst
> > --- a/Documentation/bpf/libbpf/libbpf_naming_convention.rst
> > +++ b/Documentation/bpf/libbpf/libbpf_naming_convention.rst
[...]
Ah, please disregard, I missed that Alexei had already merged this.
Thanks for the cleanup.
next prev parent reply other threads:[~2023-01-30 14:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 6:39 [PATCH 00/35] Documentation: correct lots of spelling errors (series 1) Randy Dunlap
2023-01-27 6:39 ` [PATCH 04/35] Documentation: bpf: correct spelling Randy Dunlap
2023-01-27 8:29 ` Bagas Sanjaya
2023-01-28 19:38 ` Alexei Starovoitov
2023-01-30 14:24 ` David Vernet
2023-01-30 14:26 ` David Vernet [this message]
2023-01-28 10:48 ` (subset) [PATCH 00/35] Documentation: correct lots of spelling errors (series 1) Mark Brown
2023-01-28 20:30 ` patchwork-bot+netdevbpf
2023-01-31 16:28 ` (subset) " Catalin Marinas
2023-02-14 16:57 ` Martin K. Petersen
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=Y9fTs88hb84+TFLn@maniforge \
--to=void@manifault.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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