linux-kernel - Re: linux-next: build failure after merge of the sound tree (Was: 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: <20101226235928.GA18334@opensource.wolfsonmicro.com>
Date:	Sun, 26 Dec 2010 23:59:29 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Takashi Iwai <tiwai@...e.de>, 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 tree (Was:
	Re: linux-next: build failure after merge of the sound-asoc tree)

On Mon, Dec 27, 2010 at 10:49:51AM +1100, Stephen Rothwell wrote:
> On Thu, 23 Dec 2010 02:12:12 +0000 Mark Brown <broonie@...nsource.wolfsonmicro.com> wrote:

> > above which can't build on x86 as x86 lacks generic hardirqs.  I've
> > pushed up a change which ifdefs out all the tracepoints when things are
> > built modular, but it seems unfortunate that x86 isn't doing the right
> > thing here, whatever ARM is doing seems to DTRT.

> The first of those errors is now present in the sound tree, so I have
> used the version of the sound tree that would have been in next-20101223
> if I had released it.

Hrm?  I thought you merged the ASoC tree before the sound tree, in which
case the above is somehwat surprising.  If the ASoC tree merged OK then
Takashi it should be a simple case of pulling my for-2.6.38 branch to
resolve the issue.
--
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/