public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: nigel@nigel.suspend2.net, linux-pm@lists.osdl.org
Subject: Re: [RFC/PATCH 1/2] swsusp: preserve boot-time printk output after resume
Date: Fri, 27 Apr 2007 14:57:34 +0200	[thread overview]
Message-ID: <20070427125734.GK22250@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0704271551250.12688@sbz-30.cs.Helsinki.FI>

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.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-04-27 12:57 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 [this message]
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
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=20070427125734.GK22250@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-pm@lists.osdl.org \
    --cc=nigel@nigel.suspend2.net \
    --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