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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CACRpkdbc3dWpTvsojUvjCitdBMJ6F9U+uhSoJLt3-zFc=azhxw@mail.gmail.com>
Date:	Thu, 10 May 2012 14:12:51 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Ola Lilja <ola.o.lilja@...ricsson.com>,
	Liam Girdwood <lrg@...com>, 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, May 10, 2012 at 11:09 AM, Mark Brown
<broonie@...nsource.wolfsonmicro.com> wrote:
> On Thu, May 10, 2012 at 10:30:50AM +0200, Linus Walleij wrote:
>
>>  menuconfig SND_SOC_UX500
>>         tristate "SoC Audio support for Ux500 platform"
>>         depends on SND_SOC
>> +       depends on MFD_DB8500_PRCMU
>>         help
>>                 Say Y if you want to enable ASoC-support for
>>                 any of the Ux500 platforms (e.g. U8500).
>
> I applied this (without your signoff as you didn't supply one so it'll
> show up as my patch,

Sorry, Acked-by :-)

>> But it seems it has a wider dependency on some MOP500 board
>> stuff being merged first, which is more of a problem I think, part
>> of that is pending in the Ux500 tree.
>
> If this has a dependency on a particular board the driver is badly
> broken, this is the driver for the SoC I2S controller so it should work
> with any board.
>
> That said in terms of applying the change the arch/arm stuff shouldn't
> be an issue - it was just registering devices and clocks.  The driver
> won't load until the two trees are merged but that's not an issue, it's
> not going to run anyway if we delay applying it.

Yeah let's see if it works, if it breaks again we can just pull it out
and defer it.

Yours,
Linus Walleij
--
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/