From: patchwork-bot+linux-riscv@kernel.org
To: Nick Hu <nick.hu@sifive.com>
Cc: linux-riscv@lists.infradead.org, anup@brainfault.org,
rafael@kernel.org, daniel.lezcano@linaro.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, greentime.hu@sifive.com,
zong.li@sifive.com
Subject: Re: [PATCH v2 0/2] cpuidle: riscv-sbi: Allow cpuidle pd used by other devices
Date: Fri, 18 Oct 2024 19:30:31 +0000 [thread overview]
Message-ID: <172927983117.3213860.9782496340545347046.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240814054434.3563453-1-nick.hu@sifive.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 14 Aug 2024 13:44:32 +0800 you wrote:
> Add this patchset so the devices that inside the cpu/cluster power domain
> can use the cpuidle pd to register the genpd notifier to handle the PM
> when cpu/cluster is going to enter a deeper sleep state.
>
> Nick Hu (2):
> cpuidle: riscv-sbi: Move sbi_cpuidle_init to arch_initcall
> cpuidle: riscv-sbi: Add cpuidle_disabled() check
>
> [...]
Here is the summary with links:
- [v2,1/2] cpuidle: riscv-sbi: Move sbi_cpuidle_init to arch_initcall
https://git.kernel.org/riscv/c/f8a23e3b79d6
- [v2,2/2] cpuidle: riscv-sbi: Add cpuidle_disabled() check
https://git.kernel.org/riscv/c/27b4d6aa29ab
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:[~2024-10-18 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 5:44 Nick Hu
2024-08-14 5:44 ` [PATCH v2 1/2] cpuidle: riscv-sbi: Move sbi_cpuidle_init to arch_initcall Nick Hu
2024-08-23 7:09 ` Anup Patel
2024-08-14 5:44 ` [PATCH v2 2/2] cpuidle: riscv-sbi: Add cpuidle_disabled() check Nick Hu
2024-08-23 7:09 ` Anup Patel
2024-08-22 4:22 ` [PATCH v2 0/2] cpuidle: riscv-sbi: Allow cpuidle pd used by other devices Nick Hu
2024-10-18 19: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=172927983117.3213860.9782496340545347046.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=daniel.lezcano@linaro.org \
--cc=greentime.hu@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nick.hu@sifive.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rafael@kernel.org \
--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
all inboxes | Powered by JetHome®