From: Kukjin Kim <kgene@kernel.org>
To: "'Sylwester Nawrocki'" <s.nawrocki@samsung.com>,
"'Chanwoo Choi'" <cw00.choi@samsung.com>
Cc: tomasz.figa@gmail.com, sw0312.kim@samsung.com,
kyungmin.park@samsung.com, inki.dae@samsung.com,
geunsik.lim@samsung.com, linux-samsung-soc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: RE: [PATCHv3 0/2] clk: samsung: Add clock controller driver for Exynos4415 SoC
Date: Tue, 28 Oct 2014 13:09:59 +0900 [thread overview]
Message-ID: <02dd01cff265$0a846060$1f8d2120$@kernel.org> (raw)
In-Reply-To: <544E20E3.5030609@samsung.com>
Sylwester Nawrocki wrote:
>
> On 27/10/14 02:11, Chanwoo Choi wrote:
> > Chanwoo Choi (2):
> > clk: samsung: exynos4415: Add clocks using common clock framework
> > clk: samsung: Document binding for Exynos4415 clock controller
>
> Added both to my tree, thanks. In future please put DT binding
> documentation first in the series, before the actual driver patch.
>
Hi Sylwester,
Can you please provide a topic branch for clk-exynos4415? Because exynos4415 dt
file needs inclusion of following header files.
+#include <dt-bindings/clock/exynos4415.h>
+#include <dt-bindings/clock/exynos-audss-clk.h>
Thanks,
Kukjin
next prev parent reply other threads:[~2014-10-28 4:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 1:11 [PATCHv3 0/2] clk: samsung: Add clock controller driver for Exynos4415 SoC Chanwoo Choi
2014-10-27 1:11 ` [PATCHv3 1/2] clk: samsung: exynos4415: Add clocks using common clock framework Chanwoo Choi
2014-10-27 1:11 ` [PATCHv3 2/2] clk: samsung: Document binding for Exynos4415 clock controller Chanwoo Choi
2014-10-27 10:39 ` [PATCHv3 0/2] clk: samsung: Add clock controller driver for Exynos4415 SoC Sylwester Nawrocki
2014-10-27 10:49 ` Chanwoo Choi
2014-10-28 4:09 ` Kukjin Kim [this message]
2014-10-31 10:03 ` 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='02dd01cff265$0a846060$1f8d2120$@kernel.org' \
--to=kgene@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=geunsik.lim@samsung.com \
--cc=inki.dae@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=sw0312.kim@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).