From: Stefan Seyfried <seife@suse.de>
To: Pavel Machek <pavel@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH] swsusp: misc cleanups [4/4]
Date: Sun, 24 Apr 2005 22:43:15 +0200 [thread overview]
Message-ID: <426C04E3.9070508@suse.de> (raw)
In-Reply-To: <20050424202230.GC30088@elf.ucw.cz>
Pavel Machek wrote:
> That would not work, anyway. You want the messages from drivers,
> too... and drivers are not going to prepend "swsusp".
Yes it would. I do not need driver messages if the reason is "no swap
partition" or something like that ;-))
> Ultimately, cleaning up "suspend screen" so that it is not too scary
> for non-technical users might be nice... It means killing some debug
> messages from drivers, too.
I'd just sweep it under the bootsplash carpet. Then we have both:
possibility to debug and nice progressbar as long as everything works
fine :-)
--
Stefan Seyfried, QA / R&D Team Mobile Devices, SUSE LINUX Nürnberg.
"Any ideas, John?"
"Well, surrounding them's out."
next prev parent reply other threads:[~2005-04-24 20:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 21:20 [PATCH] swsusp: misc cleanups [0/4] Rafael J. Wysocki
2005-04-23 21:25 ` [PATCH] swsusp: misc cleanups [1/4] Rafael J. Wysocki
2005-04-23 22:05 ` Pavel Machek
2005-04-23 21:29 ` [PATCH] swsusp: misc cleanups [2/4] Rafael J. Wysocki
2005-04-23 22:02 ` Pavel Machek
2005-04-23 21:34 ` [PATCH] swsusp: misc cleanups [3/4] Rafael J. Wysocki
2005-04-23 22:18 ` Pavel Machek
2005-04-24 10:41 ` Rafael J. Wysocki
2005-04-24 20:23 ` Pavel Machek
2005-04-23 21:38 ` [PATCH] swsusp: misc cleanups [4/4] Rafael J. Wysocki
2005-04-23 22:07 ` Pavel Machek
2005-04-24 10:30 ` Rafael J. Wysocki
2005-04-24 20:20 ` Pavel Machek
2005-04-24 10:57 ` Stefan Seyfried
2005-04-24 20:22 ` Pavel Machek
2005-04-24 20:43 ` Stefan Seyfried [this message]
2005-04-24 21:03 ` Pavel Machek
2005-04-23 21:58 ` [PATCH] swsusp: misc cleanups [0/4] Pavel Machek
2005-04-24 10:06 ` 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=426C04E3.9070508@suse.de \
--to=seife@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.