public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Li, Fei" <fei.li@intel.com>
Cc: "rjw@sisk.pl" <rjw@sisk.pl>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"ldewangan@nvidia.com" <ldewangan@nvidia.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Liu, Chuansheng" <chuansheng.liu@intel.com>
Subject: Re: [PATCH] pm: print the name of failed suspend function for platform device
Date: Mon, 18 Mar 2013 19:37:43 -0700	[thread overview]
Message-ID: <20130319023743.GB21789@kroah.com> (raw)
In-Reply-To: <BEC9F67575FA1E429CA7CF5AE9BE3634421912@SHSMSX102.ccr.corp.intel.com>

On Tue, Mar 19, 2013 at 02:05:02AM +0000, Li, Fei wrote:
> > > Print more info when platform device suspend function failed.
> > > Without this patch, we can not get the real platform device suspend
> > > API info.
> > >
> > > Example without this patch:
> > > pm_op(): platform_pm_suspend+0x0/0x50 returns -11
> > > PM: Device power.0 failed to suspend: error -11
> > >
> > > And with this patch:
> > > platform_pm_suspend(): power_suspend+0x0/0x30 returns -11
> > > pm_op(): platform_pm_suspend+0x0/0x80 returns -11
> > > PM: Device power.0 failed to suspend: error -11
> > 
> > How does that help someone out?  One extra line?  What is that going to
> > allow a user to now do?
> >
> Thanks for your comments.
> 
> The intention is to print relatively complete call path for convenience of
> debugging in case of error. With this, we can know the exact name of
> the concrete failed function.

And what was the failed function here, and what would that enable you to
do?

> Besides, currently such information is printed with level KERN_ERR,
> and can be tuned through console_loglevel to avoid the possible impact
> to end user.

Huh?  End users see KERN_ERR.

> Do you think it make sense?

no.  But this is Rafael's file, so I'll defer to him.

greg k-h


  reply	other threads:[~2013-03-19  2:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18  5:58 [PATCH] pm: print the name of failed suspend function for platform device Li Fei
2013-03-18 16:05 ` Greg KH
2013-03-19  2:05   ` Li, Fei
2013-03-19  2:37     ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-02-05  5:13 fli24
2013-03-11  1:41 ` Liu, Chuansheng
2013-03-15 19:20   ` gregkh
2013-03-16  1:22     ` Liu, Chuansheng
2013-03-16  3:54       ` gregkh

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=20130319023743.GB21789@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=chuansheng.liu@intel.com \
    --cc=fei.li@intel.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.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