From: Joe Perches <joe@perches.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] power: user: Standardize "Syncing filesystems ..." message
Date: Fri, 05 Jun 2015 08:07:38 -0700 [thread overview]
Message-ID: <1433516858.2658.44.camel@perches.com> (raw)
In-Reply-To: <20150605103727.GA6054@amd>
On Fri, 2015-06-05 at 12:37 +0200, Pavel Machek wrote:
> On Thu 2015-06-04 11:36:48, Joe Perches wrote:
> > Instead of a two individual printks that would generally be
> > emitted on a single line, emit 2 lines to make the start
> > and end of the synchronization more easily timeable.
[]
> > diff --git a/kernel/power/user.c b/kernel/power/user.c
[]
> > @@ -221,9 +221,9 @@ static long snapshot_ioctl(struct file *filp, unsigned int cmd,
> > if (data->frozen)
> > break;
> >
> > - printk("Syncing filesystems ... ");
> > + printk("Syncing filesystems ...\n");
> > sys_sync();
> > - printk("done.\n");
> > + printk("Syncing filesystems: done\n");
>
> You converted " ..." -> "..." elsewhere, so why not here?
Missed that one.
> Is splitting message to two lines a good idea?
I think the "done" is unnecessary actually.
As there's no newline on the first, printk is
async and can be interleaved by other threads.
next prev parent reply other threads:[~2015-06-05 15:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 18:36 [PATCH 0/6] kernel: power: Neaten PM: logging Joe Perches
2015-06-04 18:36 ` [PATCH 1/6] power: hibernate: Use separate messages for "Syncing filesystems" Joe Perches
2015-06-08 23:35 ` Rafael J. Wysocki
2015-06-08 23:23 ` Joe Perches
2015-06-09 9:20 ` Pavel Machek
2015-06-04 18:36 ` [PATCH 2/6] power: process: Standardize "freezing process" messages Joe Perches
2015-06-04 18:36 ` [PATCH 3/6] power: suspend: Standardize "Syncing filesystems" messages Joe Perches
2015-06-04 18:36 ` [PATCH 4/6] power: swap: Standardize "Image <loading/saving>" messages Joe Perches
2015-06-04 18:36 ` [PATCH 5/6] power: user: Standardize "Syncing filesystems ..." message Joe Perches
2015-06-05 10:37 ` Pavel Machek
2015-06-05 15:07 ` Joe Perches [this message]
2015-06-06 13:36 ` Pavel Machek
2015-06-04 18:36 ` [PATCH 6/6] power: Use pr_fmt and pr_<level> Joe Perches
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=1433516858.2658.44.camel@perches.com \
--to=joe@perches.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--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
Powered by JetHome