From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for December 27
Date: Mon, 27 Dec 2010 15:38:43 +0000 [thread overview]
Message-ID: <20101227153843.GA13400@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20101228022027.8519be82.sfr@canb.auug.org.au>
On Tue, Dec 28, 2010 at 02:20:27AM +1100, Stephen Rothwell wrote:
> I got this error after merging the sound tree:
> ERROR: "__tracepoint_snd_soc_jack_irq" [sound/soc/codecs/snd-soc-wm8962.ko] undefined!
> after that, I merged the old version of the sound tree. I then merged
> the sound-asoc tree and go the same error. I presumed that you had fixed
> the other error:
> ERROR: "__tracepoint_snd_soc_jack_irq" [sound/soc/codecs/snd-soc-wm8903.ko] undefined!
> in the sound-asoc tree and then that version of the sound-asoc tree had
> been merged into the sound tree.
To my knowledge I'd fixed everything. However, it looks like there's a
typo in the wm8962 ifdef to work around the x86 failure which was
causing the problem; since you hadn't mentioned that you'd encountered
any issue after I'd done the previous fix I'd no idea that this had
happened and it had appeared that the problem with Takashi's tree was
simply that he'd not merged up the fix.
Fixed now, anyway. Please do report if you see any more issues.
next prev parent reply other threads:[~2010-12-27 15:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 6:04 linux-next: Tree for December 27 Stephen Rothwell
2010-12-27 8:04 ` Sedat Dilek
2010-12-27 9:11 ` Stephen Rothwell
2010-12-27 9:55 ` Sedat Dilek
2010-12-27 12:09 ` Sedat Dilek
2010-12-27 11:38 ` Mark Brown
2010-12-27 15:20 ` Stephen Rothwell
2010-12-27 15:38 ` Mark Brown [this message]
2010-12-27 14:36 ` Piotr Hosowicz
2010-12-27 14:48 ` Sedat Dilek
2010-12-27 14:57 ` Piotr Hosowicz
2010-12-27 15:08 ` Sedat Dilek
2010-12-27 15:13 ` Piotr Hosowicz
2010-12-27 15:45 ` Piotr Hosowicz
2010-12-27 16:16 ` Sedat Dilek
2010-12-28 14:27 ` Piotr Hosowicz
2010-12-28 15:09 ` Piotr Hosowicz
2010-12-27 19:21 ` linux-next: Tree for December 27 (drivers/target/) Randy Dunlap
2010-12-27 22:47 ` Nicholas A. Bellinger
2010-12-27 19:55 ` [PATCH -next] ocfs2: fix build for OCFS2_FS_STATS not enabled Randy Dunlap
2010-12-27 20:52 ` Joel Becker
2010-12-27 21:41 ` Randy Dunlap
2010-12-27 19:57 ` linux-next: Tree for December 27 (drivers/target) Randy Dunlap
2010-12-27 22:49 ` Nicholas A. Bellinger
2010-12-28 15:08 ` James Bottomley
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=20101227153843.GA13400@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox