lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 30 Apr 2010 07:45:07 -0700
From:	Greg KH <greg@...ah.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Diego Giagio <diego@...gio.com>, Daniel Mack <daniel@...aq.de>
Subject: Re: linux-next: build failure after merge of the staging-next tree

On Fri, Apr 30, 2010 at 03:50:52PM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> After merging the staging-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/net/usb/ipheth.c: In function 'ipheth_alloc_urbs':
> drivers/net/usb/ipheth.c:131: error: implicit declaration of function 'usb_buffer_alloc'
> drivers/net/usb/ipheth.c:134: warning: assignment makes pointer from integer without a cast
> drivers/net/usb/ipheth.c:141: warning: assignment makes pointer from integer without a cast
> drivers/net/usb/ipheth.c:153: error: implicit declaration of function 'usb_buffer_free'
> 
> Caused by commit 3cc96f50329227fbf34de2459491901b6ee1c98c ("USB: rename
> usb_buffer_alloc() and usb_buffer_free() users") from the usb tree
> interacting with commit a19259c3d589a014e5f47f148f74dfc44422c82b
> ("drivers/net/usb: Add new driver ipheth") which entered Linus' tree about
> April 25 via the net tree.
> 
> I applied the following fixup patch for today.

Thanks, I'll be sending in the patch that adds the api call to Linus
today so that the individual trees can make these changes.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ