From: patchwork-bot+linux-riscv@kernel.org
To: Heiko Stuebner <heiko@sntech.de>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
christoph.muellner@vrull.eu, philipp.tomsich@vrull.eu,
abrestic@rivosinc.com, heiko.stuebner@vrull.eu
Subject: Re: [PATCH] RISC-V: Fix do_notify_resume / do_work_pending prototype
Date: Tue, 31 Jan 2023 18:30:18 +0000 [thread overview]
Message-ID: <167518981864.30496.9079639810241417567.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230118142252.337103-1-heiko@sntech.de>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 18 Jan 2023 15:22:52 +0100 you wrote:
> From: Heiko Stuebner <heiko.stuebner@vrull.eu>
>
> Commit b0f4c74eadbf ("RISC-V: Fix unannoted hardirqs-on in return to
> userspace slow-path") renamed the do_notify_resume function to
> do_work_pending but did not change the prototype in signal.h
> Do that now, as the original function does not exist anymore.
>
> [...]
Here is the summary with links:
- RISC-V: Fix do_notify_resume / do_work_pending prototype
https://git.kernel.org/riscv/c/285b6a18daf1
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-01-31 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 14:22 [PATCH] RISC-V: Fix do_notify_resume / do_work_pending prototype Heiko Stuebner
2023-01-18 15:10 ` Andrew Jones
2023-01-18 15:40 ` Conor Dooley
2023-01-27 13:59 ` Heiko Stübner
2023-01-31 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=167518981864.30496.9079639810241417567.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=abrestic@rivosinc.com \
--cc=christoph.muellner@vrull.eu \
--cc=heiko.stuebner@vrull.eu \
--cc=heiko@sntech.de \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=philipp.tomsich@vrull.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.