Re: linux-next: build failure after merge of the sound-asoc tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Mark,

On Thu, 11 Aug 2011 13:06:23 +0900 Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> On Thu, Aug 11, 2011 at 01:11:29PM +1000, Stephen Rothwell wrote:
> 
> > Caused by commit 40045a85df0e ("ASoC: Fix SPI driver binding for WM8987").
> 
> No it wasn't, it was there already.  Anyway, should be fixed now.

Thanks.

> Do you have any idea what you're doing to turn on this detection?  It
> really shouldn't be something that's specific to the x86 build but
> there's nothing obvious I can see that does it.

My x86_64 allmodconfig build is (effectively) done like this (I am using
gcc v4.5.2):

echo CONFIG_PROFILE_ALL_BRANCHES=n >../x86_64_allmodconfig.except
echo CONFIG_DEBUG_INFO=n >>../x86_64_allmodconfig.except
echo CONFIG_X86_DECODER_SELFTEST=n >>../x86_64_allmodconfig.except
KCONFIG_ALLCONFIG=../x86_64_allmodconfig.except \
        make O=../x86_64_allmodconfig allmodconfig
make O=../x86_64_allmodconfig -j48 -s

> Out of interest you used to carry reverts for commits when you'd
> identified them but that seems not to happen any more?

It depends on when I find a problem.  If I find a build problem
immediately after mergeing a particular tree, I reset linux-next and use
the previous version of the tree instead.  If I do not find the problem
until after I have completely merged all the trees, I may revert a
problem commit, or add a patch (is there is an interaction between two
trees).  In the latter case I will carry the revert or patch as long as
needed.

-- 
Cheers,
Stephen Rothwell                    sfr@xxxxxxxxxxxxxxxx
http://www.canb.auug.org.au/~sfr/

Attachment: pgpzUzqXCiu5R.pgp
Description: PGP signature


[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux