From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
LKML <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Len Brown <lenb@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: [PATCH v2 0/4] PM: Replace "freeze" with "s2idle" in item names related to suspend-to-idle
Date: Thu, 10 Aug 2017 00:11:54 +0200 [thread overview]
Message-ID: <4362123.MquenKSW7f@aspire.rjw.lan> (raw)
In-Reply-To: <1912685.WjJGzNPQ5e@aspire.rjw.lan>
On Saturday, August 5, 2017 2:55:34 PM CEST Rafael J. Wysocki wrote:
> Hi Everyone,
>
> The term "suspend-to-idle" (and its short form "s2idle") was invented after
> introducing support for the system state it refers to. At that time, the
> feature was called "freeze", kind of for the lack of a better idea how to
> call it.
>
> It would not be a problem if it wasn't confusing, but alas it is. The word
> "freeze" is quite heavily loaded in the PM terminology. It is related to
> the freezing of tasks, the freezing of filesystems (which isn't only used
> for PM for that matter), and one of the phases of handling devices during
> hibernation (and during resume from it) is called "freeze", which is reflected
> in the names of PM callbacks used by it.
>
> To avoid that confusion, the following patches change the names of various
> items related to suspend-to-idle by replacing the word "freeze" in them
> with "s2idle".
>
> The series is on top of current linux-next.
The v2 addresses the comment from Peter that PM_SUSPEND_S2IDLE had too many
"suspends" in it, so it is now replaced with PM_SUSPEND_TO_IDLE. No other
changes.
Thanks,
Rafael
next prev parent reply other threads:[~2017-08-09 22:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-05 12:55 [PATCH 0/4] PM: Replace "freeze" with "s2idle" in item names related to suspend-to-idle Rafael J. Wysocki
2017-08-05 12:56 ` [PATCH 1/4] PM / s2idle: Rename PM_SUSPEND_FREEZE to PM_SUSPEND_S2IDLE Rafael J. Wysocki
2017-08-07 8:49 ` Peter Zijlstra
2017-08-07 11:57 ` Rafael J. Wysocki
2017-08-07 12:00 ` Rafael J. Wysocki
2017-08-05 12:58 ` [PATCH 2/4] PM / s2idle: Rename freeze_state enum and related items Rafael J. Wysocki
2017-08-05 12:59 ` [PATCH 3/4] PM / s2idle: Rename ->enter_freeze to ->enter_s2idle Rafael J. Wysocki
2017-08-05 13:00 ` [PATCH 4/4] PM / s2idle: Rename platform operations structure Rafael J. Wysocki
2017-08-09 22:11 ` Rafael J. Wysocki [this message]
2017-08-09 22:13 ` [PATCH v2 1/4] PM / s2idle: Rename PM_SUSPEND_FREEZE to PM_SUSPEND_TO_IDLE Rafael J. Wysocki
2017-08-09 22:13 ` [PATCH v2 2/4] PM / s2idle: Rename freeze_state enum and related items Rafael J. Wysocki
2017-08-09 22:14 ` [PATCH v2 3/4] PM / s2idle: Rename ->enter_freeze to ->enter_s2idle Rafael J. Wysocki
2017-08-09 22:15 ` [PATCH v2 4/4] PM / s2idle: Rename platform operations structure Rafael J. Wysocki
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=4362123.MquenKSW7f@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=daniel.lezcano@linaro.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
/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).