From: patchwork-bot+linux-riscv@kernel.org
To: Fangrui Song <maskray@google.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: replace deprecated scall with ecall
Date: Tue, 20 Jun 2023 19:40:23 +0000 [thread overview]
Message-ID: <168729002322.20607.3530889477319155290.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230423223210.126948-1-maskray@google.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Sun, 23 Apr 2023 22:32:10 +0000 you wrote:
> scall is a deprecated alias for ecall. ecall is used in several places,
> so there is no assembler compatibility concern.
>
> Signed-off-by: Fangrui Song <maskray@google.com>
> ---
> arch/riscv/kernel/entry.S | 4 ++--
> arch/riscv/kernel/vdso/rt_sigreturn.S | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
Here is the summary with links:
- riscv: replace deprecated scall with ecall
https://git.kernel.org/riscv/c/4681dacadeef
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-06-20 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 22:32 [PATCH] riscv: replace deprecated scall with ecall Fangrui Song
2023-05-11 22:41 ` Fangrui Song
2023-06-13 21:51 ` Fangrui Song
2023-06-20 19:30 ` Palmer Dabbelt
2023-06-20 19:40 ` patchwork-bot+linux-riscv [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=168729002322.20607.3530889477319155290.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maskray@google.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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