From: mturquette@baylibre.com (Michael Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/3] arm64/clk: EXYNOS: Consolidate Exynos7 symbol
Date: Tue, 16 Feb 2016 14:31:58 -0800 [thread overview]
Message-ID: <20160216223158.2278.48998@quark.deferred.io> (raw)
In-Reply-To: <1455603632-11158-1-git-send-email-k.kozlowski@samsung.com>
Quoting Krzysztof Kozlowski (2016-02-15 22:20:29)
> Hi,
>
> Patchset attempts to remove the ARCH_EXYNOS7 symbol.
>
> I rebased this on top of James':
> - clk: Move vendor's Kconfig into CCF menu section
> http://www.spinics.net/lists/devicetree/msg111953.html
>
> The third patch depends on previous ones so one way of merging this
> would be to prepare a tag from clk tree with first two patches
> and the dependency. The last third patch would go through arm-soc.
I've done this locally and things look good. I'm just waiting for Acks
to patch #2 and I'll merge patches #1 and #2 and provide a stable tag
named clk-samsung-kconfig, based on v4.5-rc1.
These patches were not based on -rc1, but the fixups were trivial so I'm
fine with them.
Regards,
Mike
>
> Changes since v4:
> =================
> 1. Rebased on "clk: Move vendor's Kconfig into CCF menu section"
> existing in clock tree.
> 2. Re-work patch 2/3 (see specific changelog).
>
> Changes since v3:
> =================
> 1. Rebase on next-20160127 (s3c64xx became multiplatform).
>
> Changes since v2:
> =================
> 1. Follow Arnd's advice about not enabling silently the newly added
> EXYNOS_ARM64_COMMON_CLK, when COMPILE_TEST is enabled. This was
> also a trigger for some changes in placement of Samsung clocks
> Kconfig entries...
> 2. ... which lead to introducing patch 1.
>
>
> Rationale:
> ==========
> We don't need ARCH_EXYNOS7 symbol because all ARMv8 platforms should
> fall under generic ARCH_EXYNOS. In the same time there is no sense
> in building clocks for these ARMv8 SoCs on ARMv7 builds.
>
>
> Best regards,
> Krzysztof
>
> Krzysztof Kozlowski (3):
> clk: samsung: Enable COMPILE_TEST for Samsung clocks
> clk: samsung: Don't build ARMv8 clock drivers on ARMv7
> arm64: EXYNOS: Consolidate ARCH_EXYNOS7 symbol into ARCH_EXYNOS
>
> arch/arm64/Kconfig.platforms | 11 ++---------
> arch/arm64/boot/dts/exynos/Makefile | 2 +-
> arch/arm64/configs/defconfig | 2 +-
> drivers/clk/samsung/Kconfig | 18 +++++++++++++-----
> drivers/clk/samsung/Makefile | 4 ++--
> 5 files changed, 19 insertions(+), 18 deletions(-)
>
> --
> 2.5.0
>
prev parent reply other threads:[~2016-02-16 22:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 6:20 [PATCH v5 0/3] arm64/clk: EXYNOS: Consolidate Exynos7 symbol Krzysztof Kozlowski
2016-02-16 6:20 ` [PATCH v5 1/3] clk: samsung: Enable COMPILE_TEST for Samsung clocks Krzysztof Kozlowski
2016-02-16 6:20 ` [PATCH v5 2/3] clk: samsung: Don't build ARMv8 clock drivers on ARMv7 Krzysztof Kozlowski
2016-02-17 10:03 ` Sylwester Nawrocki
2016-02-22 18:26 ` Michael Turquette
2016-02-23 0:14 ` Krzysztof Kozlowski
2016-02-16 6:20 ` [PATCH v5 3/3] arm64: EXYNOS: Consolidate ARCH_EXYNOS7 symbol into ARCH_EXYNOS Krzysztof Kozlowski
2016-02-16 22:31 ` Michael Turquette [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=20160216223158.2278.48998@quark.deferred.io \
--to=mturquette@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).