From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
James Liao <jamesjj.liao@mediatek.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: linux-next: manual merge of the clk tree with the samsung-krzk tree
Date: Tue, 16 Feb 2016 13:30:05 +0900 [thread overview]
Message-ID: <56C2A5CD.9040603@samsung.com> (raw)
In-Reply-To: <20160216151131.3e1d4cb5@canb.auug.org.au>
On 16.02.2016 13:11, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the clk tree got a conflict in:
>
> drivers/clk/Kconfig
> drivers/clk/samsung/Kconfig
>
> between commit:
>
> fa6439544887 ("clk: samsung: Enable COMPILE_TEST for Samsung clocks")
>
> from the samsung-krzk tree and commit:
>
> b9e65ebc654d ("clk: Move vendor's Kconfig into CCF menu section")
>
> from the clk tree.
>
> I fixed it up (they both had similar effects) and can carry the fix as
> necessary (no action is required).
Thanks!
Stephen, Mike,
James' b9e65ebc654d looks like a simpler approach to the same problem -
moving Samsung common clocks under COMMON_CLK.
If you agree I can rebase my patch on top of it so only COMPILE_TEST
would be added.
However my third patch in that set ("arm64: EXYNOS: Consolidate
ARCH_EXYNOS7 symbol into ARCH_EXYNOS" [0]) depends on it, so maybe you
could prepare a tag with everything? James patch + two of mine (also
"clk: samsung: Don't build ARMv8 clock drivers on ARMv7")?
Best regards,
Krzysztof
[0] http://www.spinics.net/lists/devicetree/msg111893.html
prev parent reply other threads:[~2016-02-16 4:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 4:11 linux-next: manual merge of the clk tree with the samsung-krzk tree Stephen Rothwell
2016-02-16 4:30 ` Krzysztof Kozlowski [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=56C2A5CD.9040603@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=arnd@arndb.de \
--cc=jamesjj.liao@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@codeaurora.org \
--cc=sfr@canb.auug.org.au \
/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