All of lore.kernel.org
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
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 10:07:08 -0600	[thread overview]
Message-ID: <53EA3BAC.2000104@wwwdotorg.org> (raw)
In-Reply-To: <1407852078-31309-1-git-send-email-pbrobinson@gmail.com>

On 08/12/2014 08:01 AM, Peter Robinson wrote:
> 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.

I'd rather like to get rid of CONFIG_TEGRA_xx_SOC and replace it with 
CONFIG_TEGRA, but I suppose that idea wasn't received well. So,

Acked-by: Stephen Warren <swarren@nvidia.com>

I assume this will be applied to the arm-soc tree, although 
arm at kernel.org wasn't CC'd?

> This also helps to avoid trivial merge conflicts when adding support
> for new boards.

I would expect the opposite. Most new DTs are likely to be for the most 
recent SoC, and hence this will concentrate the edits into a smaller 
part of the file and cause more merge conflicts. That is, if the changes 
are going through different trees, which they should not be, which makes 
merge conflicts less relevant.

  parent reply	other threads:[~2014-08-12 16:07 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
2014-08-12 14:37 ` Thierry Reding
2014-08-12 16:07 ` Stephen Warren [this message]
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=53EA3BAC.2000104@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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.