From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tabi Timur-B04825 <B04825@freescale.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lrg@ti.com" <lrg@ti.com>
Subject: Re: [PATCH 2/2] ASoC: fsl/powerpc: don't rely on the cell-index property
Date: Fri, 2 Dec 2011 12:18:21 +0000 [thread overview]
Message-ID: <20111202121820.GK8245@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4ED8C133.2080908@freescale.com>
On Fri, Dec 02, 2011 at 12:14:44PM +0000, Tabi Timur-B04825 wrote:
> Can you hold off on applying patch #2 for the moment? I just thought of
> something that I want to try first.
Sorry, I already applied it but just didnt' get round to replying to say
I did.
next prev parent reply other threads:[~2011-12-02 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 1:52 [PATCH 1/2] ASoC: p1022ds: add support for fsl, P1022 and fsl, P1022DS model names Timur Tabi
2011-12-02 1:52 ` [PATCH 2/2] ASoC: fsl/powerpc: don't rely on the cell-index property Timur Tabi
2011-12-02 12:14 ` Tabi Timur-B04825
2011-12-02 12:18 ` Mark Brown [this message]
2011-12-02 12:20 ` Tabi Timur-B04825
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=20111202121820.GK8245@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=B04825@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.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