public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org
Cc: linux-riscv@lists.infradead.org, aou@eecs.berkeley.edu,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	guoren@linux.alibaba.com, bjorn@rivosinc.com, heiko@sntech.de,
	conor@kernel.org, zouyipeng@huawei.com,
	linux-kernel@vger.kernel.org, palmer@rivosinc.com,
	heiko.stuebner@vrull.eu
Subject: Re: [PATCH] riscv: entry: Save a0 prior syscall_enter_from_user_mode()
Date: Tue, 11 Apr 2023 17:40:19 +0000	[thread overview]
Message-ID: <168123481962.28886.3531781273059476912.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230403065207.1070974-1-bjorn@kernel.org>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Mon,  3 Apr 2023 08:52:07 +0200 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
> 
> The RISC-V calling convention passes the first argument, and the
> return value in the a0 register. For this reason, the a0 register
> needs some extra care; When handling syscalls, the a0 register is
> saved into regs->orig_a0, so a0 can be properly restored for,
> e.g. interrupted syscalls.
> 
> [...]

Here is the summary with links:
  - riscv: entry: Save a0 prior syscall_enter_from_user_mode()
    https://git.kernel.org/riscv/c/9c2598d43510

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

      parent reply	other threads:[~2023-04-11 17:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03  6:52 [PATCH] riscv: entry: Save a0 prior syscall_enter_from_user_mode() Björn Töpel
2023-04-03 16:21 ` Conor Dooley
2023-04-04 15:06 ` Geert Uytterhoeven
2023-04-10  9:41 ` Andy Chiu
2023-04-11 17:39 ` Palmer Dabbelt
2023-04-11 17: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=168123481962.28886.3531781273059476912.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=bjorn@rivosinc.com \
    --cc=conor@kernel.org \
    --cc=guoren@linux.alibaba.com \
    --cc=heiko.stuebner@vrull.eu \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=palmer@rivosinc.com \
    --cc=paul.walmsley@sifive.com \
    --cc=zouyipeng@huawei.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