From: Rahul Sharma <r.sh.open@gmail.com>
To: Tomasz Figa <tomasz.figa@gmail.com>
Cc: Rahul Sharma <rahul.sharma@samsung.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Mike Turquette <mturquette@linaro.org>,
Kukjin Kim <kgene.kim@samsung.com>,
sunil joshi <joshi@samsung.com>
Subject: Re: [PATCH v6 0/2] clk: exynos: add support for exynos5260 SoC
Date: Mon, 28 Apr 2014 11:57:35 +0530 [thread overview]
Message-ID: <CAPdUM4Nxaa2DO3CEm61ti3ewE--5CkTF_uL_Cyf3oLd_r0TAeA@mail.gmail.com> (raw)
In-Reply-To: <CAPdUM4NC+8Sw-gC2anb56oemOtqu9-Dy3PopGHY7oqcwmp-Jig@mail.gmail.com>
Hi Tomasz,
Is there anything pending with this patchset? Please consider this for 3.16.
Regards,
Rahul Sharma.
On 24 March 2014 08:58, Rahul Sharma <r.sh.open@gmail.com> wrote:
> Thanks Tomasz,
>
> Please let me know if any concern.
> Meanwhile I will post dt patches with "clock" and "clock-names" properties
> added for each controller node.
>
> Regards,
> Rahul Sharma.
>
>
> On 24 March 2014 03:50, Tomasz Figa <tomasz.figa@gmail.com> wrote:
>> Hi Rahul,
>>
>>
[snip]
>>
>> Looks good to me, will apply if no comments show up for few more days.
>>
>> Best regards,
>> Tomasz
prev parent reply other threads:[~2014-04-28 6:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 20:45 [PATCH v6 0/2] clk: exynos: add support for exynos5260 SoC Rahul Sharma
2014-03-23 20:45 ` [PATCH v6 1/2] clk/exynos5260: add macros and documentation for exynos5260 Rahul Sharma
2014-03-23 20:45 ` [PATCH v6 2/2] clk/exynos5260: add clock file " Rahul Sharma
2014-03-23 22:20 ` [PATCH v6 0/2] clk: exynos: add support for exynos5260 SoC Tomasz Figa
2014-03-24 3:28 ` Rahul Sharma
2014-04-28 6:27 ` Rahul Sharma [this message]
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=CAPdUM4Nxaa2DO3CEm61ti3ewE--5CkTF_uL_Cyf3oLd_r0TAeA@mail.gmail.com \
--to=r.sh.open@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=joshi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=rahul.sharma@samsung.com \
--cc=tomasz.figa@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).