linux-kernel - Re: linux-next: staging tree build failure

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 9 Dec 2009 12:30:02 -0800
From:	Greg KH <greg@...ah.com>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	"David S. Miller" <davem@...emloft.net>,
	linux-next@...r.kernel.org,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: staging tree build failure

On Wed, Dec 09, 2009 at 10:29:22AM -0500, Alan Stern wrote:
> On Wed, 9 Dec 2009, Stephen Rothwell wrote:
> 
> > Hi Greg,
> > 
> > Today's linux-next build (x86_64 allmodconfig) failed like this:
> > 
> > drivers/net/usb/kaweth.c: In function 'kaweth_open':
> > drivers/net/usb/kaweth.c:719: error: implicit declaration of function 'usb_autopm_enable'
> > 
> > Caused by commit b3f937e6ddf3e60ed9b4c26349b7b171dffdd010 ("USB: prepare
> > for changover to Runtime PM framework").
> > 
> > I have reverted that commit for today.
> 
> This should have been okay because of Oliver's patch:
> 
> 	http://marc.info/?l=linux-netdev&m=125071045301270&w=2
> 
> which removed the offending reference.  Hasn't it been merged yet?  
> It was submitted back in August.

Hm, I thought I saw this in David's network tree in linux-next, but
perhaps that was the wifi and one other patch, I didn't look for the
kaweth patch.

David, any ideas if the patch above was just dropped for some reason.
If it was just overlooked, I can take it through my tree, as I depend on
it to not break the build.

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/