From: Kazuki Hashimoto <kazukih0205@gmail.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Hector Martin <marcan@marcan.st>,
Kazuki Hashimoto <kazukih0205@gmail.com>
Subject: [PATCH 0/2] s2idle fixes for systems without cpuidle
Date: Tue, 11 Jul 2023 14:54:20 +0900 [thread overview]
Message-ID: <20230711-cpuidle-v1-0-f391224b3140@gmail.com> (raw)
Changes in V2:
Redo implementation following input from Hector Martin
Changes in V3:
Rewrite commit message following input from Rafael J. Wysocki
---
Kazuki Hashimoto (2):
cpuidle: Don't pass any values to cpuidle_not_available
PM: s2idle: Fully prevent the system from entering s2idle when cpuidle isn't supported
drivers/cpuidle/cpuidle.c | 6 ++++--
include/linux/cpuidle.h | 6 ++----
kernel/power/main.c | 12 +++++++++---
kernel/power/suspend.c | 5 +++++
kernel/sched/idle.c | 2 +-
5 files changed, 21 insertions(+), 10 deletions(-)
---
base-commit: 8fc3b8f082cc2f5faa6eae315b938bc5e79c332e
change-id: 20230709-cpuidle-8c5469788f77
Best regards,
--
Kazuki Hashimoto <kazukih0205@gmail.com>
next reply other threads:[~2023-07-11 5:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 5:54 Kazuki Hashimoto [this message]
2023-07-11 5:54 ` [PATCH 1/2] cpuidle: Don't pass any values to cpuidle_not_available Kazuki Hashimoto
2023-07-11 7:42 ` Peter Zijlstra
2023-07-11 18:48 ` Kazuki Hashimoto
2023-07-11 5:54 ` [PATCH 2/2] PM: s2idle: Fully prevent the system from entering s2idle when cpuidle isn't supported Kazuki Hashimoto
2023-07-11 17:55 ` Rafael J. Wysocki
2023-07-11 18:38 ` Kazuki H
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=20230711-cpuidle-v1-0-f391224b3140@gmail.com \
--to=kazukih0205@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@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;
as well as URLs for NNTP newsgroup(s).