From: patchwork-bot+netdevbpf@kernel.org
To: Puranjay Mohan <puranjay@kernel.org>
Cc: void@manifault.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, corbet@lwn.net,
dthaler1968@googlemail.com, hawkinsw@obs.cr, bpf@vger.kernel.org,
bpf@ietf.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, puranjay12@gmail.com
Subject: Re: [PATCH bpf] bpf, docs: Fix the description of 'src' in ALU instructions
Date: Wed, 15 May 2024 16:58:12 +0000 [thread overview]
Message-ID: <171579229218.15564.16554458070344125415.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240514130303.113607-1-puranjay@kernel.org>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 14 May 2024 13:03:03 +0000 you wrote:
> An ALU instruction's source operand can be the value in the source
> register or the 32-bit immediate value encoded in the instruction. This
> is controlled by the 's' bit of the 'opcode'.
>
> The current description explicitly uses the phrase 'value of the source
> register' when defining the meaning of 'src'.
>
> [...]
Here is the summary with links:
- [bpf] bpf, docs: Fix the description of 'src' in ALU instructions
https://git.kernel.org/bpf/bpf/c/7a8030057f67
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-05-15 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 13:03 [PATCH bpf] bpf, docs: Fix the description of 'src' in ALU instructions Puranjay Mohan
2024-05-14 14:33 ` dthaler1968
2024-05-15 16:58 ` 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=171579229218.15564.16554458070344125415.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=dthaler1968@googlemail.com \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=hawkinsw@obs.cr \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=puranjay12@gmail.com \
--cc=puranjay@kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=void@manifault.com \
--cc=yonghong.song@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).