linux-kernel - Re: [PATCH] cpufreq: Fix build of s3c64xx cpufreq driver for header change

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110729151324.GD19118@opensource.wolfsonmicro.com>
Date:	Fri, 29 Jul 2011 16:13:24 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Dave Jones <davej@...hat.com>, linux-kernel@...r.kernel.org,
	cpufreq@...r.kernel.org, Kukjin Kim <kgene.kim@...sung.com>
Subject: Re: [PATCH] cpufreq: Fix build of s3c64xx cpufreq driver for header
 change

On Fri, Jul 29, 2011 at 11:08:51AM -0400, Dave Jones wrote:
> On Fri, Jul 29, 2011 at 04:01:44PM +0100, Mark Brown wrote:

>  > Possibly, but there were a bunch of other failures in the Samsung
>  > specific stuff not related to module.h which appeared today. I did run
>  > into another non-samsung module.h failure, though.  Mostly I was just
>  > surprised stuff like this was showing up so late in the merge window, I
>  > didn't spend a lot of time investigating what broke.

> wait, confused. Were you building Linus' tree, or -next ?

-next (given that the merge window is still open it should be emptying
out other than bug fixes...).
--
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/