From: patchwork-bot+linux-riscv@kernel.org
To: Yong-Xuan Wang <yongxuan.wang@sifive.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
greentime.hu@sifive.com, vincent.chen@sifive.com,
AndybnAC@gmail.com, andybnac@gmail.com, zong.li@sifive.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu
Subject: Re: [PATCH v2 0/2] riscv: signal: fix the size of signal frame
Date: Thu, 13 Feb 2025 18:30:40 +0000 [thread overview]
Message-ID: <173947144024.1330575.6054499758611770955.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241220083926.19453-1-yongxuan.wang@sifive.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 20 Dec 2024 16:39:22 +0800 you wrote:
> This series addresses two issues about the RISC-V signal frame size
> calculation. PATCH1 removes the unnecessary header preservation for the
> END header. PATCH2 reorders the apply_boot_alternatives() and
> init_rt_signal_env() to get the correct signal_minsigstksz.
>
> Yong-Xuan Wang (2):
> riscv: signal: fix signal frame size
> riscv: signal: fix signal_minsigstksz
>
> [...]
Here is the summary with links:
- [v2,1/2] riscv: signal: fix signal frame size
https://git.kernel.org/riscv/c/0eeb13956757
- [v2,2/2] riscv: signal: fix signal_minsigstksz
https://git.kernel.org/riscv/c/5338770fc74b
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:[~2025-02-13 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 8:39 [PATCH v2 0/2] riscv: signal: fix the size of signal frame Yong-Xuan Wang
2024-12-20 8:39 ` [PATCH v2 1/2] riscv: signal: fix signal frame size Yong-Xuan Wang
2025-01-06 14:00 ` Alexandre Ghiti
2024-12-20 8:39 ` [PATCH v2 2/2] riscv: signal: fix signal_minsigstksz Yong-Xuan Wang
2024-12-20 14:48 ` Andy Chiu
2025-01-06 14:07 ` Alexandre Ghiti
2025-02-13 18:30 ` 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=173947144024.1330575.6054499758611770955.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=AndybnAC@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=greentime.hu@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=vincent.chen@sifive.com \
--cc=yongxuan.wang@sifive.com \
--cc=zong.li@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