From: javier@osg•samsung.com (Javier Martinez Canillas)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v4 2/3] clk: samsung: Don't build ARMv8 clock drivers on ARMv7
Date: Thu, 28 Jan 2016 16:15:34 -0300 [thread overview]
Message-ID: <56AA68D6.50500@osg.samsung.com> (raw)
In-Reply-To: <1453941324-15742-3-git-send-email-k.kozlowski@samsung.com>
Hello Krzysztof,
On 01/27/2016 09:35 PM, 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>
>
Reviewed-by: Javier Martinez Canillas <javier@osg•samsung.com>
Also checked that for example clk-exynos5433 is not built anymore for
exynos_defconfig but it is built for allyesconfig.
Tested-by: Javier Martinez Canillas <javier@osg•samsung.com>
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2016-01-28 19:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 0:35 [PATCH v4 0/3] arm64/clk: EXYNOS: Consolidate Exynos7 symbol Krzysztof Kozlowski
2016-01-28 0:35 ` [PATCH v4 1/3] clk: samsung: Enable COMPILE_TEST for Samsung clocks Krzysztof Kozlowski
2016-01-28 19:12 ` Javier Martinez Canillas
2016-01-29 20:43 ` Stephen Boyd
2016-01-28 0:35 ` [PATCH v4 2/3] clk: samsung: Don't build ARMv8 clock drivers on ARMv7 Krzysztof Kozlowski
2016-01-28 1:23 ` Chanwoo Choi
2016-01-28 19:15 ` Javier Martinez Canillas [this message]
2016-01-29 20:43 ` Stephen Boyd
2016-01-28 0:35 ` [PATCH v4 3/3] arm64: EXYNOS: Consolidate ARCH_EXYNOS7 symbol into ARCH_EXYNOS Krzysztof Kozlowski
2016-01-28 19:16 ` Javier Martinez Canillas
2016-01-29 1:13 ` [PATCH v4 0/3] arm64/clk: EXYNOS: Consolidate Exynos7 symbol Andi Shyti
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=56AA68D6.50500@osg.samsung.com \
--to=javier@osg$(echo .)samsung.com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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