From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Olof Johansson <olof@lixom.net>,
Kevin Hilman <khilman@kernel.org>,
arm@kernel.org, linux-samsung-soc@vger.kernel.org,
Kukjin Kim <kgene@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL 1/5] ARM: dts: exynos: Artik5 topic branch for v4.7
Date: Sun, 24 Apr 2016 23:15:52 +0200 [thread overview]
Message-ID: <7068458.f0qaFCRyGK@wuerfel> (raw)
In-Reply-To: <1460541682-32417-2-git-send-email-k.kozlowski@samsung.com>
On Wednesday 13 April 2016 12:01:18 Krzysztof Kozlowski wrote:
> Topic branch for Device Tree changes for Exynos 3250 for v4.7:
>
> Merge necessary new clocks from Sylwester (used by new board) and add support
> for Exynos3250-based Artik5 board.
>
Merged into next/dt, thanks!
I see that you have modified the include/dt-bindings/clock/exynos3250.h
file. Two questions about that:
- How is this going to get synchronized with the respective driver changes
in a way that avoids breaking the build of the clk tree? Do you just
wait another merge window for that?
- Are there any other clocks that you should define now so you don't run
into dependency problems later?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/5] ARM: dts: exynos: Artik5 topic branch for v4.7
Date: Sun, 24 Apr 2016 23:15:52 +0200 [thread overview]
Message-ID: <7068458.f0qaFCRyGK@wuerfel> (raw)
In-Reply-To: <1460541682-32417-2-git-send-email-k.kozlowski@samsung.com>
On Wednesday 13 April 2016 12:01:18 Krzysztof Kozlowski wrote:
> Topic branch for Device Tree changes for Exynos 3250 for v4.7:
>
> Merge necessary new clocks from Sylwester (used by new board) and add support
> for Exynos3250-based Artik5 board.
>
Merged into next/dt, thanks!
I see that you have modified the include/dt-bindings/clock/exynos3250.h
file. Two questions about that:
- How is this going to get synchronized with the respective driver changes
in a way that avoids breaking the build of the clk tree? Do you just
wait another merge window for that?
- Are there any other clocks that you should define now so you don't run
into dependency problems later?
Arnd
next prev parent reply other threads:[~2016-04-24 21:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 10:01 [GIT PULL 0/5] ARM: EXYNOS: Stuff for v4.7 Krzysztof Kozlowski
2016-04-13 10:01 ` Krzysztof Kozlowski
2016-04-13 10:01 ` [GIT PULL 1/5] ARM: dts: exynos: Artik5 topic branch " Krzysztof Kozlowski
2016-04-13 10:01 ` Krzysztof Kozlowski
2016-04-24 21:15 ` Arnd Bergmann [this message]
2016-04-24 21:15 ` Arnd Bergmann
2016-04-25 9:01 ` Krzysztof Kozlowski
2016-04-25 9:01 ` Krzysztof Kozlowski
2016-04-25 15:53 ` Arnd Bergmann
2016-04-25 15:53 ` Arnd Bergmann
2016-04-13 10:01 ` [GIT PULL 2/5] ARM: dts: exynos: DT " Krzysztof Kozlowski
2016-04-13 10:01 ` Krzysztof Kozlowski
2016-04-24 21:18 ` Arnd Bergmann
2016-04-24 21:18 ` Arnd Bergmann
2016-04-25 9:02 ` Krzysztof Kozlowski
2016-04-25 9:02 ` Krzysztof Kozlowski
2016-04-13 10:01 ` [GIT PULL 3/5] arm64: " Krzysztof Kozlowski
2016-04-13 10:01 ` Krzysztof Kozlowski
2016-04-25 20:48 ` Arnd Bergmann
2016-04-25 20:48 ` Arnd Bergmann
2016-04-13 10:01 ` [GIT PULL 4/5] ARM: defconfig " Krzysztof Kozlowski
2016-04-13 10:01 ` Krzysztof Kozlowski
2016-04-13 10:01 ` Krzysztof Kozlowski
2016-04-25 19:08 ` Arnd Bergmann
2016-04-25 19:08 ` Arnd Bergmann
2016-04-13 10:01 ` [GIT PULL 5/5] arm64: " Krzysztof Kozlowski
2016-04-13 10:01 ` Krzysztof Kozlowski
2016-04-25 19:18 ` Arnd Bergmann
2016-04-25 19:18 ` Arnd Bergmann
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=7068458.f0qaFCRyGK@wuerfel \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
/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.