From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 3/5] arm: Clean up MACH_TYPE_xxx usage after re-sync of mach-types
Date: Sat, 28 Jan 2017 17:45:48 -0500 [thread overview]
Message-ID: <20170128224548.GE22316@bill-the-cat> (raw)
In-Reply-To: <1485394958-4746-3-git-send-email-trini@konsulko.com>
On Wed, Jan 25, 2017 at 08:42:36PM -0500, Tom Rini wrote:
> With the latest mach-types values we have many instances where we no
> longer need to define a value and a few cases where the name (but not
> value) have changed slightly.
>
> 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/20170128/b8ef3582/attachment.sig>
next prev parent reply other threads:[~2017-01-28 22:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 1:42 [U-Boot] [PATCH 1/5] arm: Re-sync with full list of MACH_TYPE_xxx values Tom Rini
2017-01-26 1:42 ` [U-Boot] [PATCH 2/5] Revert "arm: Remove unregister MACH_TYPE_xxx uses" Tom Rini
2017-01-28 22:45 ` [U-Boot] [U-Boot, " Tom Rini
2017-01-26 1:42 ` [U-Boot] [PATCH 3/5] arm: Clean up MACH_TYPE_xxx usage after re-sync of mach-types Tom Rini
2017-01-28 22:45 ` Tom Rini [this message]
2017-01-26 1:42 ` [U-Boot] [PATCH 4/5] am335x_shc: Drop MACH_TYPE usage Tom Rini
2017-01-28 22:45 ` [U-Boot] [U-Boot,4/5] " Tom Rini
2017-01-26 1:42 ` [U-Boot] [PATCH 5/5] arm: Note vendor-required status of certain MACH_TYPE values Tom Rini
2017-01-26 5:41 ` Stefan Roese
2017-01-28 22:45 ` [U-Boot] [U-Boot, " Tom Rini
2017-01-28 22:45 ` [U-Boot] [U-Boot, 1/5] arm: Re-sync with full list of MACH_TYPE_xxx values 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=20170128224548.GE22316@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