public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut.n900@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM: Update mach-types
Date: Tue, 28 Feb 2012 04:51:33 +0100	[thread overview]
Message-ID: <1330401093.1507.2.camel@konomi> (raw)
In-Reply-To: <4F4C2A64.3030100@boundarydevices.com>

> On 2/27/2012 3:56 PM, Marek Vasut wrote:
> > > |ARM: Update mach-types
> > > |
> > > |This commit updates the mach-types based on the latest in Linus's
> > > head |
> > > |Signed-off-by: Marek Vasut<marek.vasut@gmail.com>
> > > 
> > > Hi Marek,
> > > 
> > > 
> > > Can I get you to do this again? I'd the symbol for
> > > MACH_MX6Q_SABRELITE.
> > 
> > No, can you please submit the mach-types update yourself? Thank you!
> > 
> I don't think I'm trusted to do that. I think that some machines may 
> have been removed
> from Linux that u-boot may want to keep.

So these machines have to define their mach id in their config (and you need to fix them after replacing mach-types).

Since I only want to use the 
> value in 1 place,
> is it acceptable to just use the hex value instead?

No, either update the mach types (preffered) or ... Update the mach types ;)

Thanks in advance. M

  reply	other threads:[~2012-02-28  3:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27 21:56 [U-Boot] ARM: Update mach-types Troy Kisky
2012-02-27 22:56 ` Marek Vasut
2012-02-28  1:14   ` Troy Kisky
2012-02-28  3:51     ` Marek Vasut [this message]
2012-02-29  0:01       ` stefano babic
2012-02-29 20:33         ` Troy Kisky
2012-02-28  6:50 ` Dirk Behme
2012-02-28  9:28   ` Fabio Estevam
2012-02-28 13:36     ` Eric Nelson
  -- strict thread matches above, loose matches on Subject: below --
2010-02-27 23:35 [U-Boot] ARM " Tom
2009-11-15 17:55 [U-Boot] ARM update mach-types Tom

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=1330401093.1507.2.camel@konomi \
    --to=marek.vasut.n900@gmail.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