public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Guo Ren <guoren@kernel.org>
Cc: linux-riscv@lists.infradead.org, arnd@arndb.de,
	palmer@rivosinc.com, linux-arch@vger.kernel.org,
	linux-kernel@vger.kernel.org, guoren@linux.alibaba.com
Subject: Re: [PATCH] riscv: sigcontext: Correct the comment of sigreturn
Date: Wed, 12 Jul 2023 13:50:22 +0000	[thread overview]
Message-ID: <168916982203.8919.10360262283664186104.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230628091213.2908149-1-guoren@kernel.org>

Hello:

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

On Wed, 28 Jun 2023 05:12:13 -0400 you wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
> 
> The real-time signals enlarged the sigset_t type, and most architectures
> have changed to using rt_sigreturn as the only way. The riscv is one of
> them, and there is no sys_sigreturn in it. Only some old architecture
> preserved sys_sigreturn as part of the historical burden.
> 
> [...]

Here is the summary with links:
  - riscv: sigcontext: Correct the comment of sigreturn
    https://git.kernel.org/riscv/c/471aba2e4760

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



      parent reply	other threads:[~2023-07-12 13:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28  9:12 [PATCH] riscv: sigcontext: Correct the comment of sigreturn guoren
2023-07-12 13:39 ` Palmer Dabbelt
2023-07-12 13:50 ` 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=168916982203.8919.10360262283664186104.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=arnd@arndb.de \
    --cc=guoren@kernel.org \
    --cc=guoren@linux.alibaba.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@rivosinc.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