From: Tomasz Figa <t.figa@samsung.com>
To: Kukjin Kim <kgene.kim@samsung.com>, Tomasz Figa <tomasz.figa@gmail.com>
Cc: Tushar Behera <tushar.behera@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, mark.rutland@arm.com,
pawel.moll@arm.com, ijc+devicetree@hellion.org.uk,
robh+dt@kernel.org, rob@landley.net, galak@codeaurora.org,
plagnioj@jcrosoft.com, linux@maxim.org.za,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH 2/2] dt-bindings: clock: Move exynos-audss-clk.h to dt-bindings/clock
Date: Tue, 18 Mar 2014 15:32:07 +0100 [thread overview]
Message-ID: <532858E7.3040802@samsung.com> (raw)
In-Reply-To: <53277548.60300@samsung.com>
On 17.03.2014 23:20, Kukjin Kim wrote:
> On 03/10/14 09:20, Tomasz Figa wrote:
>> On 06.03.2014 07:04, Tushar Behera wrote:
>>> Most of the clock related dt-binding header files are located in
>>> dt-bindings/clock folder. It would be good to keep all the similar
>>> header files at a single location.
>>>
>>> Signed-off-by: Tushar Behera <tushar.behera@linaro.org>
>>> CC: Kukjin Kim <kgene.kim@samsung.com>
>
> Acked-by: Kukjin Kim <kgene.kim@samsung.com>
>
> Or shall I take this into samsung tree?
I guess so.
Or should this whole series go through DT tree?
Best regards,
Tomasz
next prev parent reply other threads:[~2014-03-18 14:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 6:04 [PATCH 0/2] Move header files from dt-bindings/clk to dt-bindings/clock Tushar Behera
2014-03-06 6:04 ` [PATCH 1/2] dt-bindings: clock: Move at91.h to dt-bindigs/clock Tushar Behera
2014-03-10 11:05 ` Nicolas Ferre
2014-04-18 15:53 ` Nicolas Ferre
2014-03-06 6:04 ` [PATCH 2/2] dt-bindings: clock: Move exynos-audss-clk.h to dt-bindings/clock Tushar Behera
2014-03-06 6:34 ` Sachin Kamat
2014-03-06 8:17 ` Tushar Behera
2014-03-10 0:20 ` Tomasz Figa
2014-03-17 22:20 ` Kukjin Kim
2014-03-18 14:32 ` Tomasz Figa [this message]
2014-03-20 19:32 ` Kukjin Kim
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=532858E7.3040802@samsung.com \
--to=t.figa@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@secretlab.ca \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=plagnioj@jcrosoft.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=tomasz.figa@gmail.com \
--cc=tushar.behera@linaro.org \
/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