public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dtb: move all dtb targets to common Makefile
Date: Thu, 20 Sep 2012 23:29:05 -0600	[thread overview]
Message-ID: <505BFB21.8030503@wwwdotorg.org> (raw)
In-Reply-To: <1348203840-23559-1-git-send-email-olof@lixom.net>

On 09/20/2012 11:04 PM, Olof Johansson wrote:
> Since the dtb targets have moved to arch/arm/boot/dts/Makefile, sweep
> the platforms that have had new targets added recently and move them over.
> 
> While I was at it, I also made the dtb generation more generic, i.e. if
> the platform is enabled then all dtbs for that platform will be created.

> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile

> +dtb-$(CONFIG_ARCH_BCM2835) += bcm2835-rpi-b.dtb

That's still in arch/arm/mach-bcm2835/Makefile.boot.

And I don't see any diffs for Tegra, which added some new files in the
dt and dt2 branches IIRC (e.g. commit
a3ee1293b1bec15e179b5a4c99fe07157de35202). Strangely, git log on arm-soc
for-next commit bc51b817c64e6c3b9865b87a7c3d6b9d6ea9afb2 doesn't show
any edits to arch/arm/mach-tegra/Makefile.boot even though that other
commit I mentioned did touch the file and is in the history??? I guess I
need sleep.

  parent reply	other threads:[~2012-09-21  5:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21  5:04 [PATCH] ARM: dtb: move all dtb targets to common Makefile Olof Johansson
2012-09-21  5:22 ` Simon Horman
2012-09-21  5:29 ` Stephen Warren [this message]
2012-09-21  5:41   ` Olof Johansson
2012-09-21  5:59     ` Olof Johansson
2012-09-24 17:40 ` David Brown

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=505BFB21.8030503@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox