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] [day] [month] [year] [list]
Message-ID: <20081204043822.GF18027@kroah.com>
Date:	Wed, 3 Dec 2008 20:38:22 -0800
From:	Greg KH <greg@...ah.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for December 2 (staging)

On Wed, Dec 03, 2008 at 01:19:04PM -0800, Randy Dunlap wrote:
> Greg KH wrote:
> > On Tue, Dec 02, 2008 at 10:13:36AM -0800, Randy Dunlap wrote:
> >> Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Changes since 20081201:
> >>>
> >>> Today's tree fails the powerpc allyesconfig build.
> >> Greg,
> >> FYI, the staging drivers still have lots of errors (as reported
> >> over 1 week ago; yes, I know, holiday time), but I've stopped reporting
> >> on them until I see some reason to think that fixes have been made.
> > 
> > I've fixed the errors that I can in my tree.  The majority of the errors
> > you are seeing are ones that are caused by api changes in other trees
> > that I can't fix up now in -staging until those changes go into Linus's
> > tree.
> > 
> > Which is fine, I'll fix them up when I push them to Linus, so you don't
> > have to worry about them.
> > 
> > Some of the other warnings are just due to horrible code, like the
> > drivers/staging/otus/ driver that has some looney macros that cause lots
> > of build warnings.  Those will take more work and I'm hoping that the
> > community of developers that have been helping out with the staging tree
> > will help there.
> 
> So this one is an API change or it's fixed in your tree but not in linux-next
> of 20081203?
> 
> drivers/built-in.o: In function `enable_oled':
> asus_oled.c:(.text+0x52c38): undefined reference to `usb_bulk_msg'

I thought this was fixed...

Ah, tricky, the dependancy is on CONFIG_USB_SUPPORT, not CONFIG_USB,
wierd that this snuck through.  I'll go fix this up, thanks for letting
me know.

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