From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: Shawn Guo <shawn.guo@linaro.org>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: fsl: Fix multiple symbol definitions
Date: Thu, 31 Jan 2013 15:09:39 +0800 [thread overview]
Message-ID: <20130131070937.GF7663@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20130131070658.GB31996@avionic-0098.mockup.avionic-design.de>
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
On Thu, Jan 31, 2013 at 08:06:58AM +0100, Thierry Reding wrote:
> That does indeed look much better than fiddling with the Makefile. My
> automated ARM builds of linux-next were failing for a few days because
> of this, so I guess the fix (as well as the MMC one) just hadn't made it
> into linux-next yet.
The last -next was on the 29th, once it's rebuilt the fix should be
there.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-01-31 7:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 20:24 [PATCH] ASoC: fsl: Fix multiple symbol definitions Thierry Reding
2013-01-31 1:42 ` Shawn Guo
2013-01-31 7:06 ` Thierry Reding
2013-01-31 7:09 ` Mark Brown [this message]
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=20130131070937.GF7663@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=thierry.reding@avionic-design.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).