From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] PM / core: Clean up suspend/resume diagnostic messages
Date: Sun, 13 May 2018 10:46:29 +0200 [thread overview]
Message-ID: <2450217.aSupH1P1pj@aspire.rjw.lan> (raw)
In-Reply-To: <152477804633.202432.12678470890830085798.stgit@bhelgaas-glaptop.roam.corp.google.com>
On Thursday, April 26, 2018 11:36:20 PM CEST Bjorn Helgaas wrote:
> These are pretty minor cleanups to the suspend/resume diagnostic messages.
>
> The first two are trivial. The third may break scripts that parse dmesg
> output. I looked at scripts/bootgraph.pl, and I don't think it is
> affected, but there may be others I don't know about. Let me know if there
> are.
>
> ---
>
> Bjorn Helgaas (3):
> PM / core: Remove unused initcall_debug_report() arguments
> PM / core: Simplify initcall_debug_report() timing
> PM / core: Use dev_printk() and symbols in suspend/resume diagnostics
>
>
> drivers/base/power/main.c | 37 +++++++++++++++++--------------------
> 1 file changed, 17 insertions(+), 20 deletions(-)
>
All [1-3/3] applied, thanks!
prev parent reply other threads:[~2018-05-13 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 21:36 [PATCH 0/3] PM / core: Clean up suspend/resume diagnostic messages Bjorn Helgaas
2018-04-26 21:36 ` [PATCH 1/3] PM / core: Remove unused initcall_debug_report() arguments Bjorn Helgaas
2018-04-26 21:36 ` [PATCH 2/3] PM / core: Simplify initcall_debug_report() timing Bjorn Helgaas
2018-04-26 21:36 ` [PATCH 3/3] PM / core: Use dev_printk() and symbols in suspend/resume diagnostics Bjorn Helgaas
2018-05-01 21:01 ` [PATCH 0/3] PM / core: Clean up suspend/resume diagnostic messages Pavel Machek
2018-05-13 8:46 ` Rafael J. Wysocki [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=2450217.aSupH1P1pj@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=helgaas@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
/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