linux-kernel - Re: aat2870 causes build failure in current upstream

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: <20110806065312.GD13220@elte.hu>
Date:	Sat, 6 Aug 2011 08:53:12 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Jinyoung Park <jinyoungp@...dia.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: aat2870 causes build failure in current upstream


* Randy Dunlap <rdunlap@...otime.net> wrote:

> On Fri, 05 Aug 2011 09:22:47 -0700 H. Peter Anvin wrote:
> 
> > On 08/04/2011 11:03 PM, Jinyoung Park wrote:
> > > Hi,
> > > 
> > > I try to check allmodconfig error issue for aat2870 backlight driver.
> > > But I could not observing error message what you attached, building is
> > > successed.
> > > Please let me know how to reproduce allmodconfig problem for aat2870
> > > backlight driver.
> > > 
> > > This is my repro step.
> > > $ git clone
> > > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > > $ cd linux-next
> > > $ make allmodconfig
> > > $ make
> > > 
> > > Thanks,
> > > Jin.
> > > 
> > 
> > Get Linus' current tree, not linux-next.
> 
> Now fixed?  current mainline i386 allmodconfig builds OK for me.

Yeah, works ok for me with latest -git as well so something fixed it.

Thanks,

	Ingo
--
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/