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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20110801002933.GB20641@opensource.wolfsonmicro.com>
Date:	Mon, 1 Aug 2011 09:29:34 +0900
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	Dave Jones <davej@...hat.com>, linux-kernel@...r.kernel.org,
	patches@...nsource.wolfsonmicro.com,
	Randy Dunlap <rdunlap@...otime.net>
Subject: Re: [PATCH] cpufreq: Fix build of s3c64xx cpufreq driver for header
 change

On Sat, Jul 30, 2011 at 01:44:25PM -0400, Paul Gortmaker wrote:
> On 11-07-29 11:19 AM, Mark Brown wrote:

> > Some header change has removed an implicit include of module.h, breaking
> > the build due to the use of THIS_MODULE. Fix that.

> Thanks, I'll apply it to the module.h cleanup branch that is soaking
> in linux-next.

There's a bunch of other changes fixing issues with this floating around
- Randy Dunlap sent something for a regulator driver the other day and
I've got a couple of other Samsung patches I sent on the basis that this
must have been caused by a change in the Samsung headers.
--
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/