From: patchwork-bot+netdevbpf@kernel.org
To: Yixun Lan <dlan@gentoo.org>
Cc: linux-riscv@lists.infradead.org, bjorn@kernel.org,
bpf@vger.kernel.org, palmer@dabbelt.com, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, kafai@fb.com,
songliubraving@fb.com, yhs@fb.com, john.fastabend@gmail.com,
kpsingh@kernel.org, paul.walmsley@sifive.com,
aou@eecs.berkeley.edu, chenhengqi@outlook.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv, libbpf: use a0 for RC register
Date: Thu, 07 Jul 2022 14:40:13 +0000 [thread overview]
Message-ID: <165720481355.13867.6133173423267200694.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220706140204.47926-1-dlan@gentoo.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 6 Jul 2022 22:02:04 +0800 you wrote:
> According to the RISC-V calling convention register usage here[1],
> a0 is used as return value register, so rename it to make it consistent
> with the spec.
>
> [1] section 18.2, table 18.2
> https://riscv.org/wp-content/uploads/2015/01/riscv-calling.pdf
>
> [...]
Here is the summary with links:
- riscv, libbpf: use a0 for RC register
https://git.kernel.org/bpf/bpf-next/c/935dc35c7531
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:[~2022-07-07 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 14:02 [PATCH] riscv, libbpf: use a0 for RC register Yixun Lan
2022-07-07 8:53 ` Björn Töpel
2022-07-07 14:04 ` Amjad Ouled-Ameur
2022-07-07 14: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=165720481355.13867.6133173423267200694.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenhengqi@outlook.com \
--cc=daniel@iogearbox.net \
--cc=dlan@gentoo.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).