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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110811035552.GB15906@opensource.wolfsonmicro.com>
Date:	Thu, 11 Aug 2011 13:06:23 +0900
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, Aug 11, 2011 at 01:11:29PM +1000, Stephen Rothwell wrote:

> sound/soc/codecs/snd-soc-wm8750: struct spi_device_id is 40 bytes.  The last of 2 is:
> 0x77 0x6d 0x38 0x39 0x38 0x37 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 
> FATAL: sound/soc/codecs/snd-soc-wm8750: struct spi_device_id is not terminated with a NULL entry!

> Caused by commit 40045a85df0e ("ASoC: Fix SPI driver binding for WM8987").

No it wasn't, it was there already.  Anyway, should be fixed now.

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.

Out of interest you used to carry reverts for commits when you'd
identified them but that seems not to happen any more?
--
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/