From: David Vernet <void@manifault.com>
To: Dave Thaler <dthaler1968=40googlemail.com@dmarc.ietf.org>
Cc: bpf@vger.kernel.org, bpf@ietf.org, Dave Thaler <dthaler1968@gmail.com>
Subject: Re: [Bpf] [PATCH bpf-next] Introduce concept of conformance groups
Date: Tue, 9 Jan 2024 10:10:49 -0600 [thread overview]
Message-ID: <20240109161049.GA79024@maniforge> (raw)
In-Reply-To: <20240108214231.5280-1-dthaler1968@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
On Mon, Jan 08, 2024 at 01:42:31PM -0800, Dave Thaler wrote:
> The discussion of what the actual conformance groups should be
> is still in progress, so this is just part 1 which only uses
> "legacy" for deprecated instructions and "basic" for everything
> else. Subsequent patches will add more groups as discussion
> continues.
>
> Signed-off-by: Dave Thaler <dthaler1968@gmail.com>
Acked-by: David Vernet <void@manifault.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: David Vernet <void@manifault.com>
To: Dave Thaler <dthaler1968=40googlemail.com@dmarc.ietf.org>
Cc: bpf@vger.kernel.org, bpf@ietf.org, Dave Thaler <dthaler1968@gmail.com>
Subject: Re: [Bpf] [PATCH bpf-next] Introduce concept of conformance groups
Date: Tue, 9 Jan 2024 10:10:49 -0600 [thread overview]
Message-ID: <20240109161049.GA79024@maniforge> (raw)
Message-ID: <20240109161049.5m20YasrOrnKYJ_ROFNE4B3C6cTsa83iHLrutCaQbbE@z> (raw)
In-Reply-To: <20240108214231.5280-1-dthaler1968@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 442 bytes --]
On Mon, Jan 08, 2024 at 01:42:31PM -0800, Dave Thaler wrote:
> The discussion of what the actual conformance groups should be
> is still in progress, so this is just part 1 which only uses
> "legacy" for deprecated instructions and "basic" for everything
> else. Subsequent patches will add more groups as discussion
> continues.
>
> Signed-off-by: Dave Thaler <dthaler1968@gmail.com>
Acked-by: David Vernet <void@manifault.com>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 76 bytes --]
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
next prev parent reply other threads:[~2024-01-09 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 21:42 [PATCH bpf-next] Introduce concept of conformance groups Dave Thaler
2024-01-08 21:42 ` [Bpf] " Dave Thaler
2024-01-09 2:16 ` Alexei Starovoitov
2024-01-09 2:16 ` Alexei Starovoitov
2024-01-09 16:10 ` David Vernet [this message]
2024-01-09 16:10 ` David Vernet
2024-01-12 2:40 ` patchwork-bot+netdevbpf
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=20240109161049.GA79024@maniforge \
--to=void@manifault.com \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=dthaler1968=40googlemail.com@dmarc.ietf.org \
--cc=dthaler1968@gmail.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.