BPF List
 help / color / mirror / Atom feed
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: Clarify that MOVSX is only for BPF_X not BPF_K
Date: Tue, 23 Jan 2024 23:40:49 +0000	[thread overview]
Message-ID: <170605324997.25186.9635969435498333979.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240118232954.27206-1-dthaler1968@gmail.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu, 18 Jan 2024 15:29:54 -0800 you wrote:
> Per discussion on the mailing list at
> https://mailarchive.ietf.org/arch/msg/bpf/uQiqhURdtxV_ZQOTgjCdm-seh74/
> the MOVSX operation is only defined to support register extension.
> 
> The document didn't previously state this and incorrectly implied
> that one could use an immediate value.
> 
> [...]

Here is the summary with links:
  - [bpf-next] bpf, docs: Clarify that MOVSX is only for BPF_X not BPF_K
    https://git.kernel.org/bpf/bpf-next/c/20e109ea9842

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-01-23 23:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 23:29 [PATCH bpf-next] bpf, docs: Clarify that MOVSX is only for BPF_X not BPF_K Dave Thaler
2024-01-18 23:29 ` [Bpf] " Dave Thaler
2024-01-18 23:45 ` David Vernet
2024-01-18 23:45   ` David Vernet
2024-01-18 23:53 ` Yonghong Song
2024-01-18 23:53   ` Yonghong Song
2024-01-23 23:40 ` 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=170605324997.25186.9635969435498333979.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox