From: patchwork-bot+netdevbpf@kernel.org
To: Dave Thaler <dthaler1968@googlemail.com>
Cc: bpf@vger.kernel.org, bpf@ietf.org, dthaler1968@gmail.com
Subject: Re: [PATCH bpf-next] bpf, docs: Use RFC 2119 language for ISA requirements
Date: Sat, 25 May 2024 17:50:33 +0000 [thread overview]
Message-ID: <171665943320.11416.15306710552463401207.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240517165855.4688-1-dthaler1968@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 17 May 2024 09:58:55 -0700 you wrote:
> Per IETF convention and discussion at LSF/MM/BPF, use MUST etc.
> keywords as requested by IETF Area Director review. Also as
> requested, indicate that documenting BTF is out of scope of this
> document and will be covered by a separate IETF specification.
>
> Added paragraph about the terminology that is required IETF boilerplate
> and must be worded exactly as such.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf, docs: Use RFC 2119 language for ISA requirements
https://git.kernel.org/bpf/bpf-next/c/a985fdca5e7e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-05-25 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 16:58 [PATCH bpf-next] bpf, docs: Use RFC 2119 language for ISA requirements Dave Thaler
2024-05-17 16:58 ` [Bpf] " Dave Thaler
2024-05-17 17:16 ` dthaler1968
2024-05-17 17:16 ` [Bpf] " dthaler1968=40googlemail.com
2024-05-20 23:18 ` David Vernet
2024-05-20 23:18 ` [Bpf] " David Vernet
2024-05-20 23:43 ` dthaler1968
2024-05-20 23:43 ` [Bpf] " dthaler1968=40googlemail.com
2024-05-25 17:50 ` patchwork-bot+netdevbpf [this message]
2024-05-26 9:01 ` [Bpf] " Christoph Hellwig
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=171665943320.11416.15306710552463401207.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=dthaler1968@gmail.com \
--cc=dthaler1968@googlemail.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.