linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Joe Perches <joe@perches.com>
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, 5 Jun 2015 12:37:27 +0200	[thread overview]
Message-ID: <20150605103727.GA6054@amd> (raw)
In-Reply-To: <06fdc51c7d2ab639729107a137b947704fd7d161.1433442778.git.joe@perches.com>

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.
> 
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
>  kernel/power/user.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/power/user.c b/kernel/power/user.c
> index 526e891..e22f6ad 100644
> --- 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?

Is splitting message to two lines a good idea?

Is it time to introduce helper function that does the sync with the
printing?

I must say that I'm to a great fan on adding more lines to hibernation
output. Eats too much vertical space on screen, etc. Do you see real
problems there or are you just trying to "improve" this?

I'm pretty sure sync timing can be easily obtained from other messages
around this one...

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2015-06-05 10:37 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 [this message]
2015-06-05 15:07     ` Joe Perches
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=20150605103727.GA6054@amd \
    --to=pavel@ucw.cz \
    --cc=joe@perches.com \
    --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;
as well as URLs for NNTP newsgroup(s).