public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	zong.li@sifive.com
Subject: Re: [PATCH] cpuidle: riscv-sbi: Add cluster_pm_enter()/exit()
Date: Sun, 28 Apr 2024 22:00:34 +0000	[thread overview]
Message-ID: <171434163471.22130.9333013244228014885.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240226065113.1690534-1-nick.hu@sifive.com>

Hello:

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

On Mon, 26 Feb 2024 14:51:13 +0800 you wrote:
> When the cpus in the same cluster are all in the idle state, the kernel
> might put the cluster into a deeper low power state. Call the
> cluster_pm_enter() before entering the low power state and call the
> cluster_pm_exit() after the cluster woken up.
> 
> Signed-off-by: Nick Hu <nick.hu@sifive.com>
> 
> [...]

Here is the summary with links:
  - cpuidle: riscv-sbi: Add cluster_pm_enter()/exit()
    https://git.kernel.org/riscv/c/3fd665f2854d

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



  reply	other threads:[~2024-04-28 22:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26  6:51 [PATCH] cpuidle: riscv-sbi: Add cluster_pm_enter()/exit() Nick Hu
2024-04-28 22:00 ` patchwork-bot+linux-riscv [this message]
2024-04-29 14:32 ` Ulf Hansson
2024-04-29 16:22   ` Nick Hu
2024-04-29 16:26     ` Nick Hu
2024-04-30  8:12       ` Ulf Hansson
2024-05-14  9:50         ` Nick Hu
2024-05-14 14:23           ` Anup Patel
2024-05-14 14:54             ` Anup Patel
2024-05-15 12:15               ` Nick Hu
2024-05-15 13:45                 ` Anup Patel
2024-05-16  4:09                   ` Nick Hu
2024-05-17  4:39                     ` Anup Patel
2024-05-23  3:26                       ` Nick Hu
2024-05-24 10:41                       ` Ulf Hansson
2024-05-24 12:54                         ` Anup Patel
2024-04-29 20:59   ` Palmer Dabbelt

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=171434163471.22130.9333013244228014885.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=anup@brainfault.org \
    --cc=daniel.lezcano@linaro.org \
    --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