linux-kernel - linux-next: build failure after merge of the s5p 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-next>] [day] [month] [year] [list]

Message-Id: <20120103180854.e9bff732db50c0fa9afd2967@canb.auug.org.au>
Date:	Tue, 3 Jan 2012 18:08:54 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Kukjin Kim <kgene.kim@...sung.com>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Greg KH <greg@...ah.com>, Linus <torvalds@...ux-foundation.org>
Subject: linux-next: build failure after merge of the s5p tree

Hi Kukjin,

After merging the s5p tree, today's linux-next build (powerpc
ppc64_defconfig) failed badly.   The problem is that you have merged into
your tree a version of the driver-core tree that I reported broken on Dec
28.

Presumably you merged the driver-core tree to fix up some conflicts I
have reported.  Don't do that, please.  Either leave them for Linus to
fix up, or do a merge of Linus' tree after he has merged the (hopefully
fixed) driver-core tree during the merge window. Or send him your tree
unmerged with the merged version available for him to use if he wants to.

I have used the s5p tree from next-20111228 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped