From: Jiri Slaby <jirislaby@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-pm@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] PM / Hibernate: swap, use KERN_CONT
Date: Sat, 10 Oct 2009 14:19:25 +0200 [thread overview]
Message-ID: <4AD07BCD.1000902@gmail.com> (raw)
In-Reply-To: <20091010121504.GB1943@ucw.cz>
On 10/10/2009 02:15 PM, Pavel Machek wrote:
> On Sat 2009-10-10 14:00:24, Jiri Slaby wrote:
>> Use KERN_CONT in save_image for printks. So that anybody won't
>> try to add a loglevel.
>
> Someone has a big, pending patch to switch to pr_*. Should we take
> that instead?
I have no problem with that at all.
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Slaby <jirislaby@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: rjw@sisk.pl, linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] PM / Hibernate: swap, use KERN_CONT
Date: Sat, 10 Oct 2009 14:19:25 +0200 [thread overview]
Message-ID: <4AD07BCD.1000902@gmail.com> (raw)
In-Reply-To: <20091010121504.GB1943@ucw.cz>
On 10/10/2009 02:15 PM, Pavel Machek wrote:
> On Sat 2009-10-10 14:00:24, Jiri Slaby wrote:
>> Use KERN_CONT in save_image for printks. So that anybody won't
>> try to add a loglevel.
>
> Someone has a big, pending patch to switch to pr_*. Should we take
> that instead?
I have no problem with that at all.
next prev parent reply other threads:[~2009-10-10 12:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 12:00 [PATCH 1/1] PM / Hibernate: swap, use KERN_CONT Jiri Slaby
2009-10-10 12:00 ` Jiri Slaby
2009-10-10 12:15 ` Pavel Machek
2009-10-10 12:15 ` Pavel Machek
2009-10-10 12:19 ` Jiri Slaby [this message]
2009-10-10 12:19 ` Jiri Slaby
2009-10-28 22:08 ` Rafael J. Wysocki
2009-10-28 22:08 ` 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=4AD07BCD.1000902@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
/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.