Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
In-Reply-To: <20230628091213.2908149-1-guoren@kernel.org>
References: <20230628091213.2908149-1-guoren@kernel.org>
Subject: Re: [PATCH] riscv: sigcontext: Correct the comment of sigreturn
Message-Id: <168916917326.11308.11157139765378457247.b4-ty@rivosinc.com>
Date:   Wed, 12 Jul 2023 06:39:33 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Cc:     linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
        linux-riscv@lists.infradead.org, Guo Ren <guoren@kernel.org>
From:   Palmer Dabbelt <palmer@rivosinc.com>
To:     Arnd Bergmann <arnd@arndb.de>, guoren@kernel.org
Precedence: bulk


On Wed, 28 Jun 2023 05:12:13 -0400, guoren@kernel.org wrote:
> 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.
> 
> 

Applied, thanks!

[1/1] riscv: sigcontext: Correct the comment of sigreturn
      https://git.kernel.org/palmer/c/471aba2e4760

Best regards,
-- 
Palmer Dabbelt <palmer@rivosinc.com>