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: <s5hzkuct5qt.wl%tiwai@suse.de>
Date:	Mon, 18 Oct 2010 07:44:10 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Liam Girdwood <lrg@...mlogic.co.uk>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Peter Hsiang <Peter.Hsiang@...im-ic.com>
Subject: Re: linux-next: build failure after merge of the sound-asoc tree

At Mon, 18 Oct 2010 14:39:25 +1100,
Stephen Rothwell wrote:
> 
> Hi all,
> 
> On Mon, 18 Oct 2010 14:29:34 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > After merging the sound-asoc tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> > 
> > sound/soc/codecs/max98088.c:28:28: error: sound/max98088.h: No such file or directory
> 	.
> 	.
> > 
> > Caused by commit e65d255a5a610ce9e185e0df855250706aca7c21 ("ASoC: Add
> > max98088 CODEC driver").
> > 
> > Please, please build test what you are submitting.
> > 
> > I have used the sound-asoc tree from next-20101015 for today.
> 
> I have also had to use the version of the sound tree from next-20101015
> since it had merged the sound-asoc tree.

Mark now fixed it (just removed the driver), and I pulled it to sound
tree, too.  Sorry for inconvenience.


Takashi
--
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/