public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux PM <linux-pm@osdl.org>
Subject: Re: [RFC][PATCH -mm] swsusp userland interface: additional ioctl
Date: Mon, 30 Jan 2006 22:59:28 +0100	[thread overview]
Message-ID: <20060130215928.GJ2250@elf.ucw.cz> (raw)
In-Reply-To: <200601302215.10384.rjw@sisk.pl>

[-- Attachment #1: Type: text/plain, Size: 909 bytes --]

Hi!

> > > > > The appended patch provides an additional ioctl() for the swsusp userland
> > > > > interface that will allow the suspending and/or resuming utilities to change
> > > > > the kernel log level at the time of suspend/resume (or even set it to 0 if
> > > > > they are going to use some frame buffer graphics etc.).
> > > > 
> > > > klogd can already change loglevel... It should be possible to use that
> > > > to silence suspend, no?
> > > 
> > > Well, no.  Currently the kernel changes the log level to 10 unconditionally
> > > in pm_prepare_console() (that's the reason for the patch, BTW).
> > 
> > Can we just kill that log-level setting? It may have been useful in
> > the past, but I do not think it has right to live any more.
> 
> Sure, we can:
> 
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>

ACK and thanks. Patches that remve code are always good.

							Pavel
-- 
Thanks, Sharp!

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2006-01-30 21:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-29 21:56 [RFC][PATCH -mm] swsusp userland interface: additional ioctl Rafael J. Wysocki
2006-01-29 21:57 ` Pavel Machek
2006-01-29 22:46   ` Rafael J. Wysocki
2006-01-29 23:06     ` Pavel Machek
2006-01-30  4:54       ` Greg KH
2006-01-30 21:15       ` Rafael J. Wysocki
2006-01-30 21:59         ` Pavel Machek [this message]

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=20060130215928.GJ2250@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-pm@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox