From: Daniel Mack <daniel@caiaq.de>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Len Brown <len.brown@intel.com>, Magnus Damm <damm@igel.co.jp>,
Alan Stern <stern@rowland.harvard.edu>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH] drivers/base/power: be more verbose in device_pm_add()
Date: Fri, 4 Jun 2010 18:50:37 +0200 [thread overview]
Message-ID: <20100604165037.GG2695@buzzloop.caiaq.de> (raw)
In-Reply-To: <20100604164527.GA27034@suse.de>
On Fri, Jun 04, 2010 at 09:45:27AM -0700, Greg KH wrote:
> On Fri, Jun 04, 2010 at 02:17:14PM +0200, Daniel Mack wrote:
> > If a parentless device was added during a PM transaction, developers
> > might want to know which device caused the troube. Hence, output the
> > kobject's name in this case.
> >
> > Signed-off-by: Daniel Mack <daniel@caiaq.de>
> > Cc: Rafael J. Wysocki <rjw@sisk.pl>
> > Cc: Len Brown <len.brown@intel.com>
> > Cc: Greg Kroah-Hartman <gregkh@suse.de>
> > Cc: Magnus Damm <damm@igel.co.jp>
> > Cc: Alan Stern <stern@rowland.harvard.edu>
> > Cc: Randy Dunlap <randy.dunlap@oracle.com>
> > Cc: linux-pm@lists.linux-foundation.org
> > ---
> > drivers/base/power/main.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/drivers/base/power/main.c b/drivers/base/power/main.c
> > index 941fcb8..9e9fe6a 100644
> > --- a/drivers/base/power/main.c
> > +++ b/drivers/base/power/main.c
> > @@ -98,7 +98,7 @@ void device_pm_add(struct device *dev)
> > * transition is in progress in order to avoid leaving them
> > * unhandled down the road
> > */
> > - dev_WARN(dev, "Parentless device registered during a PM transaction\n");
> > + dev_WARN(dev, "Parentless device registered during a PM transaction: %s\n", kobject_name(&dev->kobj));
>
> Doesn'tthe dev_WARN call already print the name of the device? Why
> print it twice?
Erm, no it didn't. Should it have? This is what I saw:
[ 0.880646] Parentless device registered during a PM transaction
Daniel
next prev parent reply other threads:[~2010-06-04 16:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 12:17 [PATCH] drivers/base/power: be more verbose in device_pm_add() Daniel Mack
2010-06-04 16:45 ` Greg KH
2010-06-04 16:45 ` Greg KH
2010-06-04 16:50 ` Daniel Mack
2010-06-04 16:50 ` Daniel Mack [this message]
2010-06-04 17:03 ` Greg KH
2010-06-04 17:07 ` Daniel Mack
2010-06-04 17:07 ` Daniel Mack
2010-06-04 17:12 ` Greg KH
2010-06-04 17:12 ` Greg KH
2010-06-04 17:03 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-06-04 12:17 Daniel Mack
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=20100604165037.GG2695@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=damm@igel.co.jp \
--cc=gregkh@suse.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=randy.dunlap@oracle.com \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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.