From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
dg@emlix.com, Liam Girdwood <lrg@slimlogic.co.uk>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: Fix compile error for s6000-i2s.c by adding a missing ';' character
Date: Tue, 30 Nov 2010 11:24:47 +0000 [thread overview]
Message-ID: <20101130112447.GD7403@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1291081553.18485.3.camel@mola>
On Tue, Nov 30, 2010 at 09:45:53AM +0800, Axel Lin wrote:
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
> ---
> I don't have toolchain to compile s6000, I'm not able to put the error message in the commit log.
> But I know this patch indeed fixes a compile error.
Daniel already posted the same patch (and a bunch of others), just
waiting for Liam's review. The S6000 port as a whole doesn't compile
anyway at the minute (due to arch/ side issues).
prev parent reply other threads:[~2010-11-30 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 1:45 [PATCH] ASoC: Fix compile error for s6000-i2s.c by adding a missing ';' character Axel Lin
2010-11-30 11:22 ` Liam Girdwood
2010-11-30 11:24 ` 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=20101130112447.GD7403@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@gmail.com \
--cc=dg@emlix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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