From: Suman Anna <s-anna@ti.com>
To: Lokesh Vutla <lokeshvutla@ti.com>, Nishanth Menon <nm@ti.com>,
Tero Kristo <t-kristo@ti.com>, Rob Herring <robh+dt@kernel.org>
Cc: Device Tree Mailing List <devicetree@vger.kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Sekhar Nori <nsekhar@ti.com>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: [PATCH v3 1/5] arm64: dts: ti: Makefile: Use ARCH_K3 for building dtbs
Date: Tue, 8 Sep 2020 11:48:20 -0500 [thread overview]
Message-ID: <e18882ae-f6b2-7dd8-15ee-aa719888c91f@ti.com> (raw)
In-Reply-To: <20200908162252.17672-2-lokeshvutla@ti.com>
On 9/8/20 11:22 AM, Lokesh Vutla wrote:
> To allow lesser dependency and better maintainability use CONFIG_ARCH_K3
> for building dtbs for all K3 based devices. This is as per the
> discussion in [0].
>
> [0] https://lore.kernel.org/linux-arm-kernel/20200908112534.t5bgrjf7y3a6l2ss@akan/
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
> ---
> arch/arm64/boot/dts/ti/Makefile | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/ti/Makefile b/arch/arm64/boot/dts/ti/Makefile
> index 05c0bebf65d4..e7bfb16fa816 100644
> --- a/arch/arm64/boot/dts/ti/Makefile
> +++ b/arch/arm64/boot/dts/ti/Makefile
> @@ -6,6 +6,6 @@
> # Copyright (C) 2016-2018 Texas Instruments Incorporated - https://www.ti.com/
Please update the Copyright to use 2020, like 2016-2020. Minor comment, so can
be fixed up while applying.
regards
Suman
> #
>
> -dtb-$(CONFIG_ARCH_K3_AM6_SOC) += k3-am654-base-board.dtb
> +dtb-$(CONFIG_ARCH_K3) += k3-am654-base-board.dtb
>
> -dtb-$(CONFIG_ARCH_K3_J721E_SOC) += k3-j721e-common-proc-board.dtb
> +dtb-$(CONFIG_ARCH_K3) += k3-j721e-common-proc-board.dtb
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-08 16:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 16:22 [PATCH v3 0/5] arm64: Initial support for Texas Instrument's J7200 Platform Lokesh Vutla
2020-09-08 16:22 ` [PATCH v3 1/5] arm64: dts: ti: Makefile: Use ARCH_K3 for building dtbs Lokesh Vutla
2020-09-08 16:48 ` Suman Anna [this message]
2020-09-10 12:51 ` Nishanth Menon
2020-09-08 16:22 ` [PATCH v3 2/5] dt-bindings: arm: ti: Convert K3 board/soc bindings to DT schema Lokesh Vutla
2020-09-08 16:22 ` [PATCH v3 3/5] dt-bindings: arm: ti: Add bindings for J7200 SoC Lokesh Vutla
2020-09-08 16:22 ` [PATCH v3 4/5] arm64: dts: ti: Add support " Lokesh Vutla
2020-09-10 13:05 ` Vignesh Raghavendra
2020-09-10 16:54 ` Nishanth Menon
2020-09-10 17:19 ` Nishanth Menon
2020-09-10 17:54 ` Suman Anna
2020-09-10 18:20 ` Nishanth Menon
2020-09-11 2:47 ` Suman Anna
2020-09-11 13:34 ` Nishanth Menon
2020-09-08 16:22 ` [PATCH v3 5/5] arm64: dts: ti: Add support for J7200 Common Processor Board Lokesh Vutla
2020-09-10 17:23 ` Nishanth Menon
2020-09-10 17:28 ` [PATCH v3 0/5] arm64: Initial support for Texas Instrument's J7200 Platform Nishanth Menon
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=e18882ae-f6b2-7dd8-15ee-aa719888c91f@ti.com \
--to=s-anna@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.com \
/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