From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Takashi Iwai <tiwai@suse.de>, Liam Girdwood <lrg@slimlogic.co.uk>,
linux-next@vger.kernel.org, linux-kernel@vger.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)
Date: Sun, 26 Dec 2010 23:59:29 +0000 [thread overview]
Message-ID: <20101226235928.GA18334@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20101227104951.1ecad371.sfr@canb.auug.org.au>
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@opensource.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.
next prev parent reply other threads:[~2010-12-26 23:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 1:02 linux-next: build failure after merge of the sound-asoc tree Stephen Rothwell
2010-12-23 2:12 ` Mark Brown
2010-12-26 23:49 ` linux-next: build failure after merge of the sound tree (Was: Re: linux-next: build failure after merge of the sound-asoc tree) Stephen Rothwell
2010-12-26 23:59 ` Mark Brown [this message]
2010-12-27 15:16 ` Stephen Rothwell
2010-12-27 15:44 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101226235928.GA18334@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.