All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Driver Core fixes for 2.6.7-rc1
Date: Fri, 4 Jun 2004 11:42:52 -0700	[thread overview]
Message-ID: <20040604184252.GA11804@kroah.com> (raw)
In-Reply-To: <20040604182559.GI700@elf.ucw.cz>

On Fri, Jun 04, 2004 at 08:26:00PM +0200, Pavel Machek wrote:
> Hi!
> 
> > > > [PATCH] Report which device failed to suspend
> > > > 
> > > > Based on a patch from Nickolai Zeldovich <kolya@MIT.EDU> but put into the
> > > > proper place by me.
> > > 
> > > Seems good.
> > > 
> > > I'm seeing lots of problems with drivers & swsusp these days. Perhaps
> > > even printing names of devices as they are suspended is good idea?
> > 
> > You mean like the current kernel tree does if you enable
> > CONFIG_DEBUG_DRIVER?  :)
> 
> Well, something little less verbose but enabled by default would do
> the trick.

I don't think the current one is all that verbose, it just prints out
one line for every device being suspended.  And if a user is having
problems, it's quite easy to ask them to enable that option and send the
output from a failed suspend.

But if you have a patch to change it, please send it.

thanks,

greg k-h


> 								Pavel
> -- 
> 934a471f20d6580d5aad759bf0d97ddc

      reply	other threads:[~2004-06-04 18:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 21:25 [BK PATCH] Driver Core fixes for 2.6.7-rc1 Greg KH
2004-05-28 21:25 ` [PATCH] " Greg KH
2004-05-28 21:25   ` Greg KH
2004-05-28 21:25     ` Greg KH
2004-05-28 21:25       ` Greg KH
2004-05-28 21:25         ` Greg KH
2004-05-28 21:25           ` Greg KH
2004-05-28 21:25             ` Greg KH
2004-05-28 21:25               ` Greg KH
2004-06-04 12:25             ` Pavel Machek
2004-06-04 16:26               ` Greg KH
2004-06-04 18:26                 ` Pavel Machek
2004-06-04 18:42                   ` Greg KH [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=20040604184252.GA11804@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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.