* [PATCH bpf-next] bpf,docs: Rename legacy conformance group to packet
@ 2024-03-02 1:22 Dave Thaler
2024-03-02 1:22 ` [Bpf] [PATCH bpf-next] bpf, docs: " Dave Thaler
2024-03-03 5:50 ` [PATCH bpf-next] bpf,docs: " patchwork-bot+netdevbpf
0 siblings, 2 replies; 3+ messages in thread
From: Dave Thaler @ 2024-03-02 1:22 UTC (permalink / raw
To: bpf; +Cc: bpf, Dave Thaler
There could be other legacy conformance groups in the future,
so use a more descriptive name. The status of the conformance
group in the IANA registry is what designates it as legacy,
not the name of the group.
Signed-off-by: Dave Thaler <dthaler1968@gmail.com>
---
Documentation/bpf/standardization/instruction-set.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/bpf/standardization/instruction-set.rst b/Documentation/bpf/standardization/instruction-set.rst
index ffcba257e..a5ab00ac0 100644
--- a/Documentation/bpf/standardization/instruction-set.rst
+++ b/Documentation/bpf/standardization/instruction-set.rst
@@ -127,7 +127,7 @@ This document defines the following conformance groups:
* divmul32: includes 32-bit division, multiplication, and modulo instructions.
* divmul64: includes divmul32, plus 64-bit division, multiplication,
and modulo instructions.
-* legacy: deprecated packet access instructions.
+* packet: deprecated packet access instructions.
Instruction encoding
====================
@@ -710,4 +710,4 @@ class of ``LD``, a size modifier of ``W``, ``H``, or ``B``, and a
mode modifier of ``ABS`` or ``IND``. The 'dst_reg' and 'offset' fields were
set to zero, and 'src_reg' was set to zero for ``ABS``. However, these
instructions are deprecated and should no longer be used. All legacy packet
-access instructions belong to the "legacy" conformance group.
+access instructions belong to the "packet" conformance group.
--
2.40.1
^ permalink raw reply related [flat|nested] 3+ messages in thread
* [Bpf] [PATCH bpf-next] bpf, docs: Rename legacy conformance group to packet
2024-03-02 1:22 [PATCH bpf-next] bpf,docs: Rename legacy conformance group to packet Dave Thaler
@ 2024-03-02 1:22 ` Dave Thaler
2024-03-03 5:50 ` [PATCH bpf-next] bpf,docs: " patchwork-bot+netdevbpf
1 sibling, 0 replies; 3+ messages in thread
From: Dave Thaler @ 2024-03-02 1:22 UTC (permalink / raw
To: bpf; +Cc: bpf, Dave Thaler
There could be other legacy conformance groups in the future,
so use a more descriptive name. The status of the conformance
group in the IANA registry is what designates it as legacy,
not the name of the group.
Signed-off-by: Dave Thaler <dthaler1968@gmail.com>
---
Documentation/bpf/standardization/instruction-set.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/bpf/standardization/instruction-set.rst b/Documentation/bpf/standardization/instruction-set.rst
index ffcba257e..a5ab00ac0 100644
--- a/Documentation/bpf/standardization/instruction-set.rst
+++ b/Documentation/bpf/standardization/instruction-set.rst
@@ -127,7 +127,7 @@ This document defines the following conformance groups:
* divmul32: includes 32-bit division, multiplication, and modulo instructions.
* divmul64: includes divmul32, plus 64-bit division, multiplication,
and modulo instructions.
-* legacy: deprecated packet access instructions.
+* packet: deprecated packet access instructions.
Instruction encoding
====================
@@ -710,4 +710,4 @@ class of ``LD``, a size modifier of ``W``, ``H``, or ``B``, and a
mode modifier of ``ABS`` or ``IND``. The 'dst_reg' and 'offset' fields were
set to zero, and 'src_reg' was set to zero for ``ABS``. However, these
instructions are deprecated and should no longer be used. All legacy packet
-access instructions belong to the "legacy" conformance group.
+access instructions belong to the "packet" conformance group.
--
2.40.1
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH bpf-next] bpf,docs: Rename legacy conformance group to packet
2024-03-02 1:22 [PATCH bpf-next] bpf,docs: Rename legacy conformance group to packet Dave Thaler
2024-03-02 1:22 ` [Bpf] [PATCH bpf-next] bpf, docs: " Dave Thaler
@ 2024-03-03 5:50 ` patchwork-bot+netdevbpf
1 sibling, 0 replies; 3+ messages in thread
From: patchwork-bot+netdevbpf @ 2024-03-03 5:50 UTC (permalink / raw
To: Dave Thaler; +Cc: bpf, bpf, dthaler1968
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 1 Mar 2024 17:22:29 -0800 you wrote:
> There could be other legacy conformance groups in the future,
> so use a more descriptive name. The status of the conformance
> group in the IANA registry is what designates it as legacy,
> not the name of the group.
>
> Signed-off-by: Dave Thaler <dthaler1968@gmail.com>
>
> [...]
Here is the summary with links:
- [bpf-next] bpf,docs: Rename legacy conformance group to packet
https://git.kernel.org/bpf/bpf-next/c/2e0405f125b2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-03-03 5:50 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-03-02 1:22 [PATCH bpf-next] bpf,docs: Rename legacy conformance group to packet Dave Thaler
2024-03-02 1:22 ` [Bpf] [PATCH bpf-next] bpf, docs: " Dave Thaler
2024-03-03 5:50 ` [PATCH bpf-next] bpf,docs: " patchwork-bot+netdevbpf
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).