From: patchwork-bot+linux-riscv@kernel.org
To: Song Shuai <songshuaishuai@tinylab.org>
Cc: linux-riscv@lists.infradead.org, catalin.marinas@arm.com,
will@kernel.org, paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, chris@zankel.net, jcmvbkbc@gmail.com,
steven.price@arm.com, vincenzo.frascino@arm.com,
leyfoon.tan@starfivetech.com, mason.huo@starfivetech.com,
jeeheng.sia@starfivetech.com, conor.dooley@microchip.com,
ajones@ventanamicro.com, linux@armlinux.org.uk,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 0/4] Remove WARN_ON in save_processor_state
Date: Sun, 25 Jun 2023 23:20:23 +0000 [thread overview]
Message-ID: <168773522377.24181.6260932886978170161.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230609075049.2651723-1-songshuaishuai@tinylab.org>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Fri, 9 Jun 2023 15:50:45 +0800 you wrote:
> During hibernation or restoration, freeze_secondary_cpus
> checks num_online_cpus via BUG_ON, and the subsequent
> save_processor_state also does the checking with WARN_ON.
>
> In the case of CONFIG_PM_SLEEP_SMP=n, freeze_secondary_cpus
> is not defined, but the sole possible condition to disable
> CONFIG_PM_SLEEP_SMP is !SMP where num_online_cpus is always 1.
> We also don't have to check it in save_processor_state.
>
> [...]
Here is the summary with links:
- [V2,1/4] ARM: hibernate: remove WARN_ON in save_processor_state
(no matching commit)
- [V2,2/4] arm64: hibernate: remove WARN_ON in save_processor_state
(no matching commit)
- [V2,3/4] riscv: hibernate: remove WARN_ON in save_processor_state
https://git.kernel.org/riscv/c/91afbaafd6b1
- [V2,4/4] xtensa: hibernate: remove WARN_ON in save_processor_state
(no matching commit)
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:[~2023-06-25 23:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 7:50 [PATCH V2 0/4] Remove WARN_ON in save_processor_state Song Shuai
2023-06-09 7:50 ` [PATCH V2 1/4] ARM: hibernate: remove " Song Shuai
2023-06-09 7:50 ` [PATCH V2 2/4] arm64: " Song Shuai
2023-06-09 10:23 ` Will Deacon
2023-06-09 7:50 ` [PATCH V2 3/4] riscv: " Song Shuai
2023-06-10 15:39 ` Conor Dooley
2023-06-09 7:50 ` [PATCH V2 4/4] xtensa: " Song Shuai
2023-06-21 15:51 ` (subset) [PATCH V2 0/4] Remove " Catalin Marinas
2023-06-22 18:28 ` Palmer Dabbelt
2023-06-25 23:17 ` Palmer Dabbelt
2023-06-25 23:20 ` 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=168773522377.24181.6260932886978170161.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=catalin.marinas@arm.com \
--cc=chris@zankel.net \
--cc=conor.dooley@microchip.com \
--cc=jcmvbkbc@gmail.com \
--cc=jeeheng.sia@starfivetech.com \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mason.huo@starfivetech.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=songshuaishuai@tinylab.org \
--cc=steven.price@arm.com \
--cc=vincenzo.frascino@arm.com \
--cc=will@kernel.org \
/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