From: Luigi Semenzato <semenzato@google.com>
To: linux-pm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, rafael@kernel.org, gpike@google.com,
elliott@hpe.com, Luigi Semenzato <semenzato@google.com>
Subject: [PATCH v3 0/2] clarify limitations of hibernation
Date: Thu, 2 Jan 2020 15:19:38 -0800 [thread overview]
Message-ID: <20200102231940.202896-1-semenzato@google.com> (raw)
These patches aim to make it clearer under which circumstances
hibernation will function as expected. They include one documentation
change, and one change which logs more information on failure to
enter hibernation.
---- comments on patch versions ----
As suggested, v3 makes the log messages more consistent, by including the term
"hibernation" in most of them (if not all). (I think this was worth it, also
because this code doesn't change often, but we're quickly entering the region
of diminishing returns.)
v2 uses better terminology in the Documentation, and removes a suggestion
for a workaround.
-----------------------------------
Luigi Semenzato (2):
Documentation: clarify limitations of hibernation
pm: add more logging on hibernation failure
Documentation/admin-guide/pm/sleep-states.rst | 12 +++++++++-
kernel/power/hibernate.c | 23 +++++++++---------
kernel/power/snapshot.c | 24 ++++++++++++-------
3 files changed, 38 insertions(+), 21 deletions(-)
--
2.24.1.735.g03f4e72817-goog
next reply other threads:[~2020-01-02 23:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 23:19 Luigi Semenzato [this message]
2020-01-02 23:19 ` [PATCH v3 1/2] Documentation: clarify limitations of hibernation Luigi Semenzato
2020-01-07 12:14 ` Rafael J. Wysocki
2020-01-02 23:19 ` [PATCH v3 2/2] pm: add more logging on hibernation failure Luigi Semenzato
2020-01-07 12:32 ` 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=20200102231940.202896-1-semenzato@google.com \
--to=semenzato@google.com \
--cc=akpm@linux-foundation.org \
--cc=elliott@hpe.com \
--cc=gpike@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@vger.kernel.org \
--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).