From: mturquette@baylibre.com (Michael Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/3] clk: samsung: Don't build ARMv8 clock drivers on ARMv7
Date: Mon, 22 Feb 2016 10:26:56 -0800 [thread overview]
Message-ID: <20160222182656.2278.68402@quark.deferred.io> (raw)
In-Reply-To: <56C44578.5010009@samsung.com>
Quoting Sylwester Nawrocki (2016-02-17 02:03:36)
> On 16/02/16 07:20, Krzysztof Kozlowski wrote:
> > Currently the Exynos5433 (ARMv8 SoC) clock driver depends on ARCH_EXYNOS
> > so it is built also on ARMv7. This does not bring any kind of benefit.
> > There won't be a single kernel image for ARMv7 and ARMv8 SoCs (like
> > multi_v7 for ARMv7).
> >
> > Instead build clock drivers only for respective SoC's architecture.
> >
> > Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>
> Acked-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
>
Thanks for the Ack.
I've rebased patches #1 and #2 against James's b9e65ebc654d and pushed
the clk-samsung branch to the clk tree. I have deleted the
clk-samsung-kconfig branch that was blowing up the kbuild robot.
clk-samsung will not be rebased and can be used as a dependency for
arm-soc. It has been merged into clk-next.
Regards,
Mike
next prev parent reply other threads:[~2016-02-22 18:26 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 [this message]
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 ` [PATCH v5 0/3] arm64/clk: EXYNOS: Consolidate Exynos7 symbol Michael Turquette
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=20160222182656.2278.68402@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).