From: David Vernet <void@manifault.com>
To: Will Hawkins <hawkinsw@obs.cr>
Cc: bpf@vger.kernel.org, bpf@ietf.org
Subject: Re: [Bpf] [PATCH] bpf, docs: Fix small typo and define semantics of sign extension
Date: Tue, 8 Aug 2023 13:24:44 -0500 [thread overview]
Message-ID: <20230808182444.GA1158877@maniforge> (raw)
In-Reply-To: <20230808052736.182587-1-hawkinsw@obs.cr>
On Tue, Aug 08, 2023 at 01:27:32AM -0400, Will Hawkins wrote:
Hi Will,
This looks great, thanks!
Acked-by: David Vernet <void@manifault.com>
> Add additional precision on the semantics of the sign extension
> operations in eBPF. In addition, fix a very minor typo.
Just for future reference so we can have consistent nomenclature:
s/eBPF/BPF
WARNING: multiple messages have this Message-ID (diff)
From: David Vernet <void@manifault.com>
To: Will Hawkins <hawkinsw@obs.cr>
Cc: bpf@vger.kernel.org, bpf@ietf.org
Subject: Re: [Bpf] [PATCH] bpf, docs: Fix small typo and define semantics of sign extension
Date: Tue, 8 Aug 2023 13:24:44 -0500 [thread overview]
Message-ID: <20230808182444.GA1158877@maniforge> (raw)
Message-ID: <20230808182444.gwhd4oRn0kPuJgQGPJ10Iwq_3WeC-ONVai-b2IEKvOE@z> (raw)
In-Reply-To: <20230808052736.182587-1-hawkinsw@obs.cr>
On Tue, Aug 08, 2023 at 01:27:32AM -0400, Will Hawkins wrote:
Hi Will,
This looks great, thanks!
Acked-by: David Vernet <void@manifault.com>
> Add additional precision on the semantics of the sign extension
> operations in eBPF. In addition, fix a very minor typo.
Just for future reference so we can have consistent nomenclature:
s/eBPF/BPF
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
next prev parent reply other threads:[~2023-08-08 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 5:27 [Bpf] [PATCH] bpf, docs: Fix small typo and define semantics of sign extension Will Hawkins
2023-08-08 5:27 ` Will Hawkins
2023-08-08 18:24 ` David Vernet [this message]
2023-08-08 18:24 ` [Bpf] " David Vernet
2023-08-08 21:25 ` Will Hawkins
2023-08-08 21:25 ` Will Hawkins
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=20230808182444.GA1158877@maniforge \
--to=void@manifault.com \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=hawkinsw@obs.cr \
/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.