From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: Only build dtb if associated Arch and/or SoC is enabled
Date: Tue, 12 Aug 2014 16:40:41 +0200 [thread overview]
Message-ID: <20140812144040.GB9868@ulmo.nvidia.com> (raw)
In-Reply-To: <CALeDE9MMJBbs87oVsHV39tez6Eafg745GSWng-9QdnKV1FKJqQ@mail.gmail.com>
On Tue, Aug 12, 2014 at 03:25:31PM +0100, Peter Robinson wrote:
> On Tue, Aug 12, 2014 at 3:19 PM, Lucas Stach <l.stach@pengutronix.de> wrote:
> > Am Dienstag, den 12.08.2014, 15:01 +0100 schrieb Peter Robinson:
> >> A number of arches (EXYNOS/IMX/TEGRA) are separated out into finer
> >> grained definitions whether it be sub ARCH or SOC definitions. The
> >> device tree blobs should only be built if the specific option is
> >> enabled that supports that device or it might be that there's an
> >> expectation that the device is supported when in actual fact it's
> >> not. This ensures only the relevant bits are built.
> >>
> >> This also helps to avoid trivial merge conflicts when adding support
> >> for new boards.
> >>
> >> Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
> >
> > a small nitpick below, otherwise:
> > Reviewed-by: Lucas Stach <l.stach@pengutronix.de>
> >
> >> ---
> >> arch/arm/boot/dts/Makefile | 50 +++++++++++++++++++++++++++-------------------
> >> 1 file changed, 30 insertions(+), 20 deletions(-)
> >>
> >> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
> >> index b8c5cd3..e95808e 100644
> >> --- a/arch/arm/boot/dts/Makefile
> >> +++ b/arch/arm/boot/dts/Makefile
> >> @@ -64,7 +64,7 @@ dtb-$(CONFIG_ARCH_BRCMSTB) += \
> >> dtb-$(CONFIG_ARCH_DAVINCI) += da850-enbw-cmc.dtb \
> >> da850-evm.dtb
> >> dtb-$(CONFIG_ARCH_EFM32) += efm32gg-dk3750.dtb
> >> -dtb-$(CONFIG_ARCH_EXYNOS) += exynos4210-origen.dtb \
> >> +dtb-$(CONFIG_ARCH_EXYNOS4) += exynos4210-origen.dtb \
> >> exynos4210-smdkv310.dtb \
> >> exynos4210-trats.dtb \
> >> exynos4210-universal_c210.dtb \
> >> @@ -74,8 +74,8 @@ dtb-$(CONFIG_ARCH_EXYNOS) += exynos4210-origen.dtb \
> >
> > I would argue that things look a little more consistent with the
> > linebreak directly behind the "+=", as with the IMX entries. Maybe if
> > other platform maintainers agree we could change this while touching
> > things anyway. But this is only a small nitpick, so feel free to ignore.
>
> I agree but I left it as each platform had it to save extra churn as I
> wasn't sure what the exact convention was.
It seems like there isn't one convention. But consistency is always
good, so I second Lucas' proposal.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140812/007cfa84/attachment-0001.sig>
next prev parent reply other threads:[~2014-08-12 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 14:01 [PATCH] ARM: dts: Only build dtb if associated Arch and/or SoC is enabled Peter Robinson
2014-08-12 14:19 ` Lucas Stach
2014-08-12 14:25 ` Peter Robinson
2014-08-12 14:40 ` Thierry Reding [this message]
2014-08-12 14:37 ` Thierry Reding
2014-08-12 16:07 ` Stephen Warren
2014-08-18 6:39 ` Shawn Guo
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=20140812144040.GB9868@ulmo.nvidia.com \
--to=thierry.reding@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.