From: Pavel Machek <pavel@ucw.cz>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] PM / core: Clean up suspend/resume diagnostic messages
Date: Tue, 1 May 2018 23:01:15 +0200 [thread overview]
Message-ID: <20180501210115.GB9637@amd> (raw)
In-Reply-To: <152477804633.202432.12678470890830085798.stgit@bhelgaas-glaptop.roam.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
On Thu 2018-04-26 16:36:20, 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.
Looks good.
Acked-by: Pavel Machek <pavel@ucw.cz>
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-05-01 21:01 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 ` Pavel Machek [this message]
2018-05-13 8:46 ` [PATCH 0/3] PM / core: Clean up suspend/resume diagnostic messages 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=20180501210115.GB9637@amd \
--to=pavel@ucw.cz \
--cc=helgaas@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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