From: patchwork-bot+netdevbpf@kernel.org
To: Dave Thaler <dthaler1968@googlemail.com>
Cc: bpf@vger.kernel.org, bpf@ietf.org, dthaler1968@gmail.com,
void@manifault.com
Subject: Re: [PATCH bpf-next v2] bpf, docs: Use IETF format for field definitions in instruction-set.rst
Date: Sun, 03 Mar 2024 05:50:29 +0000 [thread overview]
Message-ID: <170944502959.27671.4992508067162694223.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240301222337.15931-1-dthaler1968@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 1 Mar 2024 14:23:37 -0800 you wrote:
> In preparation for publication as an IETF RFC, the WG chairs asked me
> to convert the document to use IETF packet format for field layout, so
> this patch attempts to make it consistent with other IETF documents.
>
> Some fields that are not byte aligned were previously inconsistent
> in how values were defined. Some were defined as the value of the
> byte containing the field (like 0x20 for a field holding the high
> four bits of the byte), and others were defined as the value of the
> field itself (like 0x2). This PR makes them be consistent in using
> just the values of the field itself, which is IETF convention.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf, docs: Use IETF format for field definitions in instruction-set.rst
https://git.kernel.org/bpf/bpf-next/c/4e73e1bc1abf
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:[~2024-03-03 5:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 22:23 [PATCH bpf-next v2] bpf, docs: Use IETF format for field definitions in instruction-set.rst Dave Thaler
2024-03-01 22:23 ` [Bpf] " Dave Thaler
2024-03-03 5: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=170944502959.27671.4992508067162694223.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 \
--cc=void@manifault.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