From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: Makefile.boot: Add am335x evm and bone targets
Date: Fri, 21 Sep 2012 11:54:55 -0700 [thread overview]
Message-ID: <20120921185454.GE28835@atomide.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83EAB0764@DBDE01.ent.ti.com>
* Hiremath, Vaibhav <hvaibhav@ti.com> [120910 23:56]:
> On Fri, Aug 31, 2012 at 23:24:34, Hiremath, Vaibhav wrote:
> > This adds am335x-evm and am335x-bone dtb targets to
> > 'make dtbs', just like other platforms.
> >
> > Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
> > Cc: Tony Lindgren <tony@atomide.com>
> > ---
> > arch/arm/mach-omap2/Makefile.boot | 1 +
> > 1 files changed, 1 insertions(+), 0 deletions(-)
> >
> > diff --git a/arch/arm/mach-omap2/Makefile.boot b/arch/arm/mach-omap2/Makefile.boot
> > index 6cf1c2d..1136072 100644
> > --- a/arch/arm/mach-omap2/Makefile.boot
> > +++ b/arch/arm/mach-omap2/Makefile.boot
> > @@ -7,3 +7,4 @@ dtb-$(CONFIG_ARCH_OMAP3) += omap3-beagle.dtb omap3-evm.dtb
> > dtb-$(CONFIG_ARCH_OMAP4) += omap4-panda.dtb omap4-pandaES.dtb
> > dtb-$(CONFIG_ARCH_OMAP4) += omap4-var_som.dtb omap4-sdp.dtb
> > dtb-$(CONFIG_SOC_OMAP5) += omap5-evm.dtb
> > +dtb-$(CONFIG_SOC_AM33XX) += am335x-evm.dtb am335x-bone.dtb
>
> Tony,
>
> Gentle reminder on this patch !!!
Sorry I'm behind with patches with all the clean up happening right now.
Can you please repost this for fixes the arm-soc/for-next has now moved
these to a common location for CONFIG_MULTIARCH.
The commit is 85594df2 (ARM: dtb: move all dtb targets to common Makefile).
Thanks,
Tony
prev parent reply other threads:[~2012-09-21 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 17:54 [PATCH] ARM: OMAP2+: Makefile.boot: Add am335x evm and bone targets Vaibhav Hiremath
2012-09-11 6:55 ` Hiremath, Vaibhav
2012-09-21 18:54 ` Tony Lindgren [this message]
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=20120921185454.GE28835@atomide.com \
--to=tony@atomide.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).