BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: alexei.starovoitov@gmail.com, bpf@ietf.org, bpf@vger.kernel.org,
	dthaler@microsoft.com
Subject: Re: [PATCH bpf-next] docs, bpf: Ensure IETF's BPF mailing list gets copied for ISA doc changes
Date: Sat, 11 Feb 2023 03:00:18 +0000	[thread overview]
Message-ID: <167608441806.4712.2611227890252688693.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <57619c0dd8e354d82bf38745f99405e3babdc970.1676068387.git.daniel@iogearbox.net>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri, 10 Feb 2023 23:40:31 +0100 you wrote:
> Given BPF is increasingly being used beyond just the Linux kernel, with
> implementations in NICs and other hardware, Windows, etc, there is an
> ongoing effort to document and standardize parts of the existing BPF
> infrastructure such as its ISA. As "source of truth" we decided some
> time ago to rely on the in-tree documentation, in particular, starting
> out with the Documentation/bpf/instruction-set.rst as a base for later
> RFC drafts on the ISA. Therefore, we want to ensure that changes to that
> document have bpf@ietf.org in Cc, so add a MAINTAINERS file entry with
> a section on documents related to standardization efforts. For now, this
> only relates to instruction-set.rst, and later additional files will be
> added.
> 
> [...]

Here is the summary with links:
  - [bpf-next] docs, bpf: Ensure IETF's BPF mailing list gets copied for ISA doc changes
    https://git.kernel.org/bpf/bpf-next/c/7e2a9ebe8126

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2023-02-11  3:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 22:40 [PATCH bpf-next] docs, bpf: Ensure IETF's BPF mailing list gets copied for ISA doc changes Daniel Borkmann
2023-02-11  3:00 ` 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=167608441806.4712.2611227890252688693.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bpf@ietf.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=dthaler@microsoft.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