All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-next@vger.kernel.org, "Alfred E. Heggestad" <aeh@db.org>
Subject: Re: linux-next: input tree build failure
Date: Wed, 20 Aug 2008 11:35:59 -0700	[thread overview]
Message-ID: <20080820183559.GA26064@kroah.com> (raw)
In-Reply-To: <20080820154924.51ac3495.sfr@canb.auug.org.au>

On Wed, Aug 20, 2008 at 03:49:24PM +1000, Stephen Rothwell wrote:
> Hi Greg, Dmitry,
> 
> On Tue, 19 Aug 2008 13:00:57 -0700 Greg KH <greg@kroah.com> wrote:
> >
> > No, these should all use dev_info() instead.
> > 
> > Actually, they should all use dev_dbg() and drop the #if entirely.  With
> > the dynamic dev_dbg() patch that is in -next, that will work just fine,
> > no need to rebuild modules which is almost impossible for most users to
> > do.
> 
> Today I used the following patch instead.  Dmitry, this should be able to
> be applied to your tree (I think) assuming that it is OK.

Looks good to me.

thanks,

greg k-h

  reply	other threads:[~2008-08-20 18:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19  6:31 linux-next: input tree build failure Stephen Rothwell
2008-08-19 13:01 ` Dmitry Torokhov
2008-08-19 19:59   ` Greg KH
2008-08-19 20:00 ` Greg KH
2008-08-20  5:49   ` Stephen Rothwell
2008-08-20 18:35     ` Greg KH [this message]
2008-08-22 20:29     ` Dmitry Torokhov
2008-08-22 22:15       ` Alfred E. Heggestad
2008-08-25  0:01         ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-03-10  4:49 Stephen Rothwell
2009-03-10  5:02 ` Dmitry Torokhov
2009-03-10  5:14   ` Stephen Rothwell
2009-12-07  9:03 Stephen Rothwell
2009-12-07 16:25 ` Randy Dunlap
2009-12-07 17:36   ` Dmitry Torokhov
2009-12-07 22:16     ` Stephen Rothwell
2010-01-25  5:52 Stephen Rothwell
2010-01-25  6:46 ` Dmitry Torokhov
2010-01-25  7:26   ` Tobias Klauser

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=20080820183559.GA26064@kroah.com \
    --to=greg@kroah.com \
    --cc=aeh@db.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.