linux-kernel - Re: linux-next: manual merge of the cpufreq tree with the cpufreq-current tree

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: <20120315034111.GA31961@redhat.com>
Date:	Wed, 14 Mar 2012 23:41:12 -0400
From:	Dave Jones <davej@...hat.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Russell King <rmk+kernel@....linux.org.uk>,
	Kevin Hilman <khilman@...com>,
	Jaecheol Lee <jc.lee@...sung.com>,
	Kukjin Kim <kgene.kim@...sung.com>
Subject: Re: linux-next: manual merge of the cpufreq tree with the
 cpufreq-current tree

On Thu, Mar 15, 2012 at 01:23:52PM +1100, Stephen Rothwell wrote:
 > Hi Dave,
 > 
 > Today's linux-next merge of the cpufreq tree got a conflict in
 > drivers/cpufreq/Makefile between commit b09db45c56c2 ("cpufreq: OMAP
 > driver depends CPUfreq tables") from the cpufreq-current tree and commit
 > a35c50510dd4 ("EXYNOS4X12: Add support cpufreq for EXYNOS4X12") from the
 > cpufreq tree.
 > 
 > Just context changes.  I fixed it up (see below) and can carry the fix as
 > necessary.

Argh, I've managed to get "for 3.4" patches on my fixes branch by mistake.
Given how close we are to 3.3 now, I'll just have Linus pull both branches
when 3.4 opens up.

thanks for catching this.

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