From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] omap: rx51: Remove redefinition of rx51_aic3x_data
Date: Mon, 23 Aug 2010 10:58:51 +0100 [thread overview]
Message-ID: <20100823095851.GC6061@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1282548905-10287-1-git-send-email-jhnikula@gmail.com>
On Mon, Aug 23, 2010 at 10:35:05AM +0300, Jarkko Nikula wrote:
> Redefinition of rx51_aic3x_data got introduced when merging upstread changes
> for 2.6.36 and ASoC Multi-Component Support.
>
> This must go together with multi-component commit f0fba2a.
>
> Signed-off-by: Jarkko Nikula <jhnikula@gmail.com>
> Cc: Tony Lindgren <tony@atomide.com>
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
next prev parent reply other threads:[~2010-08-23 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 7:35 [PATCH] omap: rx51: Remove redefinition of rx51_aic3x_data Jarkko Nikula
2010-08-23 9:58 ` Mark Brown [this message]
2010-08-26 20:49 ` Tony Lindgren
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=20100823095851.GC6061@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jhnikula@gmail.com \
--cc=lrg@slimlogic.co.uk \
--cc=tony@atomide.com \
/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).