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: <20110803053510.GB16141@opensource.wolfsonmicro.com>
Date:	Wed, 3 Aug 2011 14:35:11 +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 Tue, Aug 02, 2011 at 12:38:54AM -0400, Paul Gortmaker wrote:

> It is all taken care of, so you don't have to worry.  It isn't a change
> specific to any Samsung headers.  If you are interested to know the

I'm not worried, I'm now perfectly aware of the source of the breakage.
My goal is to make sure that you're aware that there are other patches
for this stuff that have been submitted separately which you're likely
to collide with if you're fixing these issues yourself.
--
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/