From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Padma Venkat <padma.kvr@gmail.com>
Cc: Padmavathi Venna <padma.v@samsung.com>,
linux-samsung-soc@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
alsa-devel@alsa-project.org, sbkim73@samsung.com,
broonie@kernel.org, kgene.kim@samsung.com, mturquette@linaro.org
Subject: Re: [PATCH V3 0/4] clk: Samsung: audss: Register audio subsytem clocks using common clk framework
Date: Sat, 01 Jun 2013 11:20:50 +0200 [thread overview]
Message-ID: <51A9BCF2.1060009@gmail.com> (raw)
In-Reply-To: <CAAgF-BfSv2WYiZrPzbdsE+7ReoncOAf1gQn+N7A2yrETFb_D4g@mail.gmail.com>
Hi,
On 06/01/2013 11:06 AM, Padma Venkat wrote:
> Actuvally I added samsung prefix when I added s5pv210 compatible name.
> But I also feel
> Exynos would be better now. I will resend the patch with Exynos prefix
> and with your reviewed-by.
Yes, that sounds like a good idea. S5PV210 is also known as Exynos3110,
and before the Exynos4210 name first appeared we had S5PV310.
Thanks,
Sylwester
WARNING: multiple messages have this Message-ID (diff)
From: sylvester.nawrocki@gmail.com (Sylwester Nawrocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 0/4] clk: Samsung: audss: Register audio subsytem clocks using common clk framework
Date: Sat, 01 Jun 2013 11:20:50 +0200 [thread overview]
Message-ID: <51A9BCF2.1060009@gmail.com> (raw)
In-Reply-To: <CAAgF-BfSv2WYiZrPzbdsE+7ReoncOAf1gQn+N7A2yrETFb_D4g@mail.gmail.com>
Hi,
On 06/01/2013 11:06 AM, Padma Venkat wrote:
> Actuvally I added samsung prefix when I added s5pv210 compatible name.
> But I also feel
> Exynos would be better now. I will resend the patch with Exynos prefix
> and with your reviewed-by.
Yes, that sounds like a good idea. S5PV210 is also known as Exynos3110,
and before the Exynos4210 name first appeared we had S5PV310.
Thanks,
Sylwester
next prev parent reply other threads:[~2013-06-01 9:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 10:02 [PATCH V3 0/4] clk: Samsung: audss: Register audio subsytem clocks using common clk framework Padmavathi Venna
2013-05-28 10:02 ` Padmavathi Venna
2013-05-28 10:02 ` [PATCH V3 1/4] ARM: samsung: use #include for all device trees Padmavathi Venna
2013-05-28 10:02 ` Padmavathi Venna
2013-05-28 10:02 ` [PATCH V3 2/4] clk: samsung: register audio subsystem clocks using common clock framework Padmavathi Venna
2013-05-28 10:02 ` Padmavathi Venna
2013-05-28 10:02 ` [PATCH V3 3/4] ARM: dts: add Exynos audio subsystem clock controller node Padmavathi Venna
2013-05-28 10:02 ` Padmavathi Venna
2013-05-28 10:02 ` [PATCH V3 4/4] ARM: dts: add clock provider information for i2s controllers in Exynos5250 Padmavathi Venna
2013-05-28 10:02 ` Padmavathi Venna
2013-06-01 8:29 ` [PATCH V3 0/4] clk: Samsung: audss: Register audio subsytem clocks using common clk framework Sylwester Nawrocki
2013-06-01 8:29 ` Sylwester Nawrocki
2013-06-01 9:06 ` Padma Venkat
2013-06-01 9:06 ` Padma Venkat
2013-06-01 9:20 ` Sylwester Nawrocki [this message]
2013-06-01 9:20 ` Sylwester Nawrocki
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=51A9BCF2.1060009@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.