All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC][PATCH] PM: Print a warning if firmware is requested when tasks are frozen
Date: Tue, 03 May 2011 11:47:23 -0400	[thread overview]
Message-ID: <15997.1304437643@localhost> (raw)
In-Reply-To: Your message of "Tue, 03 May 2011 13:02:08 +0200." <201105031302.08910.rjw@sisk.pl>

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

On Tue, 03 May 2011 13:02:08 +0200, "Rafael J. Wysocki" said:

> Although the WARN_ON output will probably not make it to the user's screen
> immediately, the resume will continue without the delay, because error code
> will be returned as soon as the WARN_ON triggers.
> 
> The user will likely notice the device not working after the resume and will
> look at dmesg output. :-)

Good point. I obviously didn't have enough caffeine to think it through. ;)

> > 2) What percent of the time the WARN_ON output will itself make the user
> > think the resume has died rather than just being slow, causing them to power
> > cycle and hope for a clean boot?
> > 
> > Maybe something like this instead?
> > 
> > 	if (WARN_ON(usermodehelper_is_disable()))) {
> > 		printk(KERN_WARNING "Resume continuing, but firmware for %s not loaded", device);
> 
> It's useful, but I'd rather do
> 
>  		dev_info(device, "firmware: %s will not be loaded\n", name);

That works too.  :)

> OK, updated patch is appended.

Looks good to me.


[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2011-05-03 15:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 22:44 [RFC][PATCH] PM: Print a warning if firmware is requested when tasks are frozen Rafael J. Wysocki
2011-05-02 23:12 ` Greg KH
2011-05-02 23:21   ` Linus Torvalds
2011-05-02 23:21     ` Linus Torvalds
2011-05-02 23:28     ` Greg KH
2011-05-03  0:59       ` Linus Torvalds
2011-05-03  0:59       ` Linus Torvalds
2011-05-03 14:05         ` Greg KH
2011-05-03 14:05         ` Greg KH
2011-05-02 23:28     ` Greg KH
2011-05-02 23:12 ` Greg KH
2011-05-02 23:30 ` Valdis.Kletnieks
2011-05-03 11:02   ` Rafael J. Wysocki
2011-05-03 11:02   ` Rafael J. Wysocki
2011-05-03 14:06     ` Greg KH
2011-05-03 14:06     ` Greg KH
2011-05-03 17:12       ` Rafael J. Wysocki
2011-05-03 17:12       ` Rafael J. Wysocki
2011-05-03 15:47     ` Valdis.Kletnieks
2011-05-03 15:47     ` Valdis.Kletnieks [this message]
2011-05-03 15:56       ` Joe Perches
2011-05-03 17:14         ` Rafael J. Wysocki
2011-05-03 17:14         ` Rafael J. Wysocki
2011-05-03 15:56       ` Joe Perches
     [not found]       ` <201105031914.18160.rjw@sisk.pl>
2011-05-03 18:03         ` Valdis.Kletnieks
2011-05-02 23:30 ` Valdis.Kletnieks
  -- strict thread matches above, loose matches on Subject: below --
2011-05-02 22:44 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=15997.1304437643@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.org \
    /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.