From: patchwork-bot+netdevbpf@kernel.org
To: David Vernet <void@manifault.com>
Cc: bpf@vger.kernel.org, bpf@ietf.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
song@kernel.org, yhs@meta.com, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
jolsa@kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, dthaler@microsoft.com
Subject: Re: [PATCH bpf-next] bpf, docs: Add myself to BPF docs MAINTAINERS entry
Date: Wed, 15 Feb 2023 16:50:17 +0000 [thread overview]
Message-ID: <167647981723.6958.10599726108070077422.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230214223553.78353-1-void@manifault.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 14 Feb 2023 16:35:53 -0600 you wrote:
> In commit 7e2a9ebe8126 ("docs, bpf: Ensure IETF's BPF mailing list gets
> copied for ISA doc changes"), a new MAINTAINERS entry was added for any
> BPF IETF documentation updates for the ongoing standardization process.
> I've been making it a point to try and review as many BPF documentation
> patches as possible, and have made a committment to Alexei to
> consistently review BPF standardization patches going forward. This
> patch adds my name as a reviewer to the MAINTAINERS entry for the
> standardization effort.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf, docs: Add myself to BPF docs MAINTAINERS entry
https://git.kernel.org/bpf/bpf-next/c/213aacb8a27b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-15 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 22:35 [PATCH bpf-next] bpf, docs: Add myself to BPF docs MAINTAINERS entry David Vernet
2023-02-15 16:50 ` patchwork-bot+netdevbpf [this message]
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=167647981723.6958.10599726108070077422.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dthaler@microsoft.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@meta.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=void@manifault.com \
--cc=yhs@meta.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