From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Padma Venkat <padma.kvr@gmail.com>
Cc: Padmavathi Venna <padma.v@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, alsa-devel@alsa-project.org,
devicetree-discuss@lists.ozlabs.org, sbkim73@samsung.com,
ben-linux@fluff.org, kgene.kim@samsung.com, lrg@ti.com,
jassisinghbrar@gmail.com
Subject: Re: [PATCH V4 0/2] Add DT support for i2s
Date: Thu, 6 Dec 2012 13:11:42 +0900 [thread overview]
Message-ID: <20121206041141.GA10867@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAAgF-Bc4t6WL4vswP6CFeSQrPZBmOuYfVt6_JoB1Za9TBX7mvA@mail.gmail.com>
On Thu, Dec 06, 2012 at 09:31:40AM +0530, Padma Venkat wrote:
> On Wed, Nov 28, 2012 at 4:17 PM, Padmavathi Venna <padma.v@samsung.com> wrote:
> > Padmavathi Venna (2):
> > ASoC: Samsung: Get I2S src_clk from clock alias id.
> > ASoC: SAMSUNG: Add DT support for i2s
> Any comments on DT support for i2s patch? If not when this patch can be pulled?
Don't send contentless pings.
I still don't really like what's going on with aliases here, I need to
understand why things are structured the way they are to say something
about that.
next prev parent reply other threads:[~2012-12-06 4:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 10:47 [PATCH V4 0/2] Add DT support for i2s Padmavathi Venna
[not found] ` <1354099669-1735-1-git-send-email-padma.v-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2012-11-28 10:47 ` [PATCH V4 1/2] ASoC: Samsung: Get I2S src_clk from clock alias id Padmavathi Venna
2012-11-28 19:18 ` Mark Brown
2012-11-28 10:47 ` [PATCH V4 2/2] ASoC: SAMSUNG: Add DT support for i2s Padmavathi Venna
2012-12-06 4:01 ` [PATCH V4 0/2] " Padma Venkat
2012-12-06 4:11 ` Mark Brown [this message]
2012-12-07 13:51 ` Grant Likely
2012-12-08 4:37 ` Padma Venkat
2012-12-09 7:26 ` Mark Brown
[not found] ` <20121209072607.GD6511-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-12-10 11:00 ` Padma Venkat
2012-12-10 14:03 ` 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=20121206041141.GA10867@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jassisinghbrar@gmail.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lrg@ti.com \
--cc=padma.kvr@gmail.com \
--cc=padma.v@samsung.com \
--cc=sbkim73@samsung.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).