All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Duncan Sands <duncan.sands@free.fr>,
	linux-usb@vger.kernel.org
Subject: Re: linux-next: Tree for August 20
Date: Wed, 20 Aug 2008 14:54:19 -0700	[thread overview]
Message-ID: <20080820215419.GA21339@kroah.com> (raw)
In-Reply-To: <20080820143656.88a03e1f.akpm@linux-foundation.org>

On Wed, Aug 20, 2008 at 02:36:56PM -0700, Andrew Morton wrote:
> On Wed, 20 Aug 2008 19:06:49 +1000
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> > I have created today's linux-next tree at
> > git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> 
> drivers/usb/atm/usbatm.c: In function 'usbatm_extract_one_cell':
> drivers/usb/atm/usbatm.c:347: error: implicit declaration of function 'warn'
> 
> due to
> 
> #define UDSL_ASSERT(x)  do { if (!(x)) warn("failed assertion '%s' at line %d", __stringify(x), __LINE__); } while(0)
> 
> which was quite clever really - neither drivers/usb/atm/usbatm.c nor
> drivers/usb/atm/usbatm.h was changed.
> 
> config: http://userweb.kernel.org/~akpm/config-akpm2.txt  (it's x86_64)

This was already fixed up, it was getting warn() from usb.h, which I'm
getting rid of.  dev_warn() should be used instead.

thanks,

greg k-h

  reply	other threads:[~2008-08-20 21:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20  9:06 linux-next: Tree for August 20 Stephen Rothwell
     [not found] ` <20080820190649.a63e3e00.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2008-08-20 21:36   ` Andrew Morton
2008-08-20 21:36     ` Andrew Morton
2008-08-20 21:54     ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-08-20  9:01 Stephen Rothwell
2010-08-20  3:33 Stephen Rothwell

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=20080820215419.GA21339@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=duncan.sands@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-usb@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.