From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Pekka J Enberg <penberg@cs.helsinki.fi>, linux-pm@lists.osdl.org
Subject: Re: [RFC/PATCH 1/2] swsusp: preserve boot-time printk output after resume
Date: Sat, 28 Apr 2007 07:21:59 +1000 [thread overview]
Message-ID: <1177708919.4737.145.camel@nigel.suspend2.net> (raw)
In-Reply-To: <20070427125734.GK22250@elf.ucw.cz>
[-- Attachment #1.1: Type: text/plain, Size: 709 bytes --]
Hi.
On Fri, 2007-04-27 at 14:57 +0200, Pavel Machek wrote:
> On Fri 2007-04-27 15:52:12, Pekka J Enberg wrote:
> > On Fri, 27 Apr 2007, Pavel Machek wrote:
> > > 1. This should not be a config option
> >
> > Ok.
>
> Unfortunately, we loose dmesg from the state saving this way, so I do
> not think it can be hardcoded, either. Best way would be to somehow
> preserve both dmesg buffers.
>
> Other way is to just control it by the define in the .c file; person
> using this is by definition kernel hacker, anyway. Or this can simply
> live like debugging patch, interested parties can apply.
That's why I made it a config option - so you can choose whether you
want it or not.
Nigel
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2007-04-27 21:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 12:25 [RFC/PATCH 1/2] swsusp: preserve boot-time printk output after resume Pekka J Enberg
2007-04-27 12:36 ` Pavel Machek
2007-04-27 12:52 ` Pekka J Enberg
2007-04-27 12:57 ` Pavel Machek
2007-04-27 14:03 ` Alan Stern
2007-04-27 14:10 ` Pekka Enberg
2007-04-27 14:36 ` Alan Stern
2007-04-27 14:32 ` Johannes Berg
2007-04-27 14:44 ` Pavel Machek
2007-04-27 21:21 ` Nigel Cunningham [this message]
2007-04-27 22:05 ` Pavel Machek
2007-04-27 22:09 ` Nigel Cunningham
2007-04-27 12:39 ` Johannes Berg
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=1177708919.4737.145.camel@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
--cc=penberg@cs.helsinki.fi \
/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