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

Date:	Wed, 3 Aug 2011 11:28:19 -0400
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.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

[Re: [PATCH] cpufreq: Fix build of s3c64xx cpufreq driver for header change] On 03/08/2011 (Wed 14:35) Mark Brown wrote:

> 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.

As long as commits end up in Linus' tree directly or in one of the
queues that are a part of the linux-next infrastructure, we have good
visibility of any conflicts thanks to Stephen R's work with next.

Paul.
--
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/