linux-kernel - Re: linux-next: build failure after merge of the sound-asoc 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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 15 Dec 2011 06:10:17 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Liam Girdwood <lrg@...mlogic.co.uk>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the sound-asoc tree

On Thu, Dec 15, 2011 at 02:38:32PM +1100, Stephen Rothwell wrote:

> Caused by commit f6a9336879ca ("ASoC: Convert wm8993 to devm_kzalloc
> ()").  I really should not be seeing this sort of build problem ...

So, the big problem with this stuff is that I can't usefully do much
with my for-next tree directly except for build test it and it's
difficult to usefully do anything with the resulting binaries especially
as the configurations which usually turn things up are generally very
slow to build.  This means I tend to mostly test on my work tree which
does contain some other code (often code which is required in order to
do an actual test) with substantially different configurations and pure
for-next tests tend to drop off the end of the day.  Doing them in
parallel tends not to work so well due to the I/O scheduler issues and
the impact on disk cache.

In this case the fix for the typo got squashed into a change that isn't
published yet by mistake.
--
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/