From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 2/3] arm: Introduce arch/arm/mach-omap2 for OMAP2 derivative platforms
Date: Mon, 21 Nov 2016 21:53:24 -0500 [thread overview]
Message-ID: <20161122025324.GZ2546@bill-the-cat> (raw)
In-Reply-To: <1478572495-20674-3-git-send-email-trini@konsulko.com>
On Mon, Nov 07, 2016 at 09:34:54PM -0500, Tom Rini wrote:
> This moves what was in arch/arm/cpu/armv7/omap-common in to
> arch/arm/mach-omap2 and moves
> arch/arm/cpu/armv7/{am33xx,omap3,omap4,omap5} in to arch/arm/mach-omap2
> as subdirectories. All refernces to the former locations are updated to
> the current locations. For the logic to decide what our outputs are,
> consolidate the tests into a single config.mk rather than including 4.
>
> Signed-off-by: Tom Rini <trini@konsulko.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161121/8b9205ef/attachment-0001.sig>
next prev parent reply other threads:[~2016-11-22 2:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 2:34 [U-Boot] [PATCH 0/3] arm: Move TI/omap related code to arch/arm/mach-omap2 Tom Rini
2016-11-08 2:34 ` [U-Boot] [PATCH 1/3] arm: Introduce ARCH_OMAP2 Tom Rini
2016-11-22 2:51 ` [U-Boot] [U-Boot,1/3] " Tom Rini
2016-11-08 2:34 ` [U-Boot] [PATCH 2/3] arm: Introduce arch/arm/mach-omap2 for OMAP2 derivative platforms Tom Rini
2016-11-22 2:53 ` Tom Rini [this message]
2016-11-08 2:34 ` [U-Boot] [PATCH 3/3] TI: Remove CONFIG_OMAP_COMMON in favor of CONFIG_ARCH_OMAP2 Tom Rini
2016-11-22 2:53 ` [U-Boot] [U-Boot, " Tom Rini
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=20161122025324.GZ2546@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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