From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Nigel Cunningham <ncunningham@crca.org.au>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Linux PCI <linux-pci@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] [PATCH 3/3] PCI PM: Make warning in pci_legacy_suspend more useful
Date: Mon, 2 Feb 2009 13:02:30 +0100 [thread overview]
Message-ID: <200902021302.31158.rjw@sisk.pl> (raw)
In-Reply-To: <1233540601.21871.10.camel@nigel-laptop>
On Monday 02 February 2009, Nigel Cunningham wrote:
> Hi again.
>
> On Sun, 2009-02-01 at 22:34 +0100, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki <rjw@sisk.pl>
> >
> > The warning in pci_legacy_suspend() would be much more useful if it
> > printed the name of the function that did the wrong thing. Make it
> > do so.
> >
> > Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> > ---
> > drivers/pci/pci-driver.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > Index: linux-2.6/drivers/pci/pci-driver.c
> > ===================================================================
> > --- linux-2.6.orig/drivers/pci/pci-driver.c
> > +++ linux-2.6/drivers/pci/pci-driver.c
> > @@ -365,7 +365,9 @@ static int pci_legacy_suspend(struct dev
> > if (pci_dev->state_saved)
> > goto Fixup;
> >
> > - if (WARN_ON_ONCE(pci_dev->current_state != PCI_D0))
> > + if (WARN_ONCE(pci_dev->current_state != PCI_D0,
> > + "PCI PM: Device state not saved by %pF\n",
> > + drv->suspend))
> > goto Fixup;
> > }
>
> Am I right in thinking that WARN_ONCE will only warn about the first
> driver that has the problem? If so, wouldn't it be better to make it
> warn about all drivers that have the problem, but only once per device?
That would be better, but I don't think we are going to see many of these
anyway. :-)
Thanks,
Rafael
next prev parent reply other threads:[~2009-02-02 12:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 21:29 [PATCH 0/3] PCI PM: More refinements of suspend-resume framework Rafael J. Wysocki
2009-02-01 21:31 ` [PATCH 1/3] PCI PM: Do not disable and enable bridges during suspend-resume Rafael J. Wysocki
2009-02-07 9:50 ` Pavel Machek
2009-02-07 13:48 ` Rafael J. Wysocki
2009-02-08 9:11 ` Pavel Machek
2009-02-08 13:23 ` Rafael J. Wysocki
2009-02-09 9:39 ` Pavel Machek
2009-02-10 0:21 ` Rafael J. Wysocki
2009-02-01 21:33 ` [PATCH 2/3] PCI PM: Let the core be more careful with respect to drivers using new framework Rafael J. Wysocki
2009-02-02 2:06 ` [linux-pm] " Nigel Cunningham
2009-02-02 12:04 ` Rafael J. Wysocki
2009-02-02 17:27 ` Rafael J. Wysocki
2009-02-01 21:34 ` [PATCH 3/3] PCI PM: Make warning in pci_legacy_suspend more useful Rafael J. Wysocki
2009-02-02 2:10 ` [linux-pm] " Nigel Cunningham
2009-02-02 12:02 ` Rafael J. Wysocki [this message]
2009-02-02 18:32 ` [PATCH 0/3] PCI PM: More refinements of suspend-resume framework Jesse Barnes
2009-02-03 3:25 ` Linus Torvalds
2009-02-03 8:26 ` 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=200902021302.31158.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=ncunningham@crca.org.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox