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:37:25 +0200 [thread overview]
Message-ID: <20140812143723.GA9868@ulmo.nvidia.com> (raw)
In-Reply-To: <1407852078-31309-1-git-send-email-pbrobinson@gmail.com>
On Tue, Aug 12, 2014 at 03:01:18PM +0100, 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.
>
> This also helps to avoid trivial merge conflicts when adding support
> for new boards.
>
> Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
> ---
> arch/arm/boot/dts/Makefile | 50 +++++++++++++++++++++++++++-------------------
> 1 file changed, 30 insertions(+), 20 deletions(-)
Acked-by: Thierry Reding <treding@nvidia.com>
-------------- 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/146a1d63/attachment.sig>
next prev parent reply other threads:[~2014-08-12 14:37 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 [this message]
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=20140812143723.GA9868@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 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).