From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Axel Lin <axel.lin@gmail.com>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Liam Girdwood <lrg@ti.com>
Subject: Re: [linux-next] ASoC: build failure if CONFIG_I2C=m && CONFIG_SPI=y && CONFIG_SND_SOC=y
Date: Wed, 24 Aug 2011 10:29:41 +0100 [thread overview]
Message-ID: <20110824092941.GC15687@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110823104253.d7768c82.rdunlap@xenotime.net>
On Tue, Aug 23, 2011 at 10:42:53AM -0700, Randy Dunlap wrote:
> I don't know if this is the same failure or just similar:
> ERROR: "regmap_exit" [drivers/mfd/wm8400-core.ko] undefined!
No, that's totally unrelated. Fixed now.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Axel Lin <axel.lin@gmail.com>,
linux-kernel@vger.kernel.org, Liam Girdwood <lrg@ti.com>,
alsa-devel@alsa-project.org
Subject: Re: [linux-next] ASoC: build failure if CONFIG_I2C=m && CONFIG_SPI=y && CONFIG_SND_SOC=y
Date: Wed, 24 Aug 2011 10:29:41 +0100 [thread overview]
Message-ID: <20110824092941.GC15687@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110823104253.d7768c82.rdunlap@xenotime.net>
On Tue, Aug 23, 2011 at 10:42:53AM -0700, Randy Dunlap wrote:
> I don't know if this is the same failure or just similar:
> ERROR: "regmap_exit" [drivers/mfd/wm8400-core.ko] undefined!
No, that's totally unrelated. Fixed now.
next prev parent reply other threads:[~2011-08-24 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 11:46 [linux-next] ASoC: build failure if CONFIG_I2C=m && CONFIG_SPI=y && CONFIG_SND_SOC=y Axel Lin
2011-08-23 17:42 ` Randy Dunlap
2011-08-23 17:42 ` Randy Dunlap
2011-08-24 9:29 ` Mark Brown [this message]
2011-08-24 9:29 ` 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=20110824092941.GC15687@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rdunlap@xenotime.net \
/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.