From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: Vasily Khoruzhick <anarsoul@gmail.com>,
alsa-devel <alsa-devel@alsa-project.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 2/2] ASoC: PXA: Fix codec address on Zipit Z2
Date: Tue, 18 Jan 2011 15:07:23 +0000 [thread overview]
Message-ID: <20110118150722.GN26498@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201101181605.47580.marek.vasut@gmail.com>
On Tue, Jan 18, 2011 at 04:05:47PM +0100, Marek Vasut wrote:
> Mark, shall I/Eric pick it via pxa-linux-2.6 or are you taking care of these two
> ?
I'll apply them, just need Liam to review them too.
next prev parent reply other threads:[~2011-01-18 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 14:54 [PATCH 1/2] ASoC: PXA: Fix jack detection on Zipit Z2 Vasily Khoruzhick
2011-01-18 14:54 ` [PATCH 2/2] ASoC: PXA: Fix codec address " Vasily Khoruzhick
2011-01-18 15:05 ` Marek Vasut
2011-01-18 15:07 ` Mark Brown [this message]
2011-01-18 15:09 ` [PATCH 1/2] ASoC: PXA: Fix jack detection " Liam Girdwood
2011-01-18 19:01 ` 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=20110118150722.GN26498@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=anarsoul@gmail.com \
--cc=lrg@slimlogic.co.uk \
--cc=marek.vasut@gmail.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).