From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: tegra: fix colibri_t20 machine type
Date: Mon, 23 Mar 2015 13:37:14 -0600 [thread overview]
Message-ID: <55106B6A.1020602@wwwdotorg.org> (raw)
In-Reply-To: <1427132590-21743-1-git-send-email-marcel@ziswiler.com>
On 03/23/2015 11:43 AM, Marcel Ziswiler wrote:
> A while ago I got Russell to change the machine type of our Colibri T20
> from COLIBRI_TEGRA2 to COLIBRI_T20 which is also reflected in his
> machine registry:
>
> http://www.arm.linux.org.uk/developer/machines/list.php?id=3323
Only "half" of the references there seem to be updated; there are still
some mentions of e.g. CONFIG_MACH_COLIBRI_TEGRA2,
MACH_TYPE_COLIBRI_TEGRA2. Perhaps it's still in flux?
Even so, this change seems fine since it does better represent the name
of the board.
Acked-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2015-03-23 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 17:43 [U-Boot] [PATCH] ARM: tegra: fix colibri_t20 machine type Marcel Ziswiler
2015-03-23 19:37 ` Stephen Warren [this message]
2015-03-26 0:45 ` Marcel Ziswiler
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=55106B6A.1020602@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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