public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] imx: Use a clear identification of an unidentified CPU type
Date: Sun, 17 Jun 2012 18:03:28 +0200	[thread overview]
Message-ID: <201206171803.28260.marex@denx.de> (raw)
In-Reply-To: <CAP9ODKoYLWcO-5W9xUcEnvtkbgJNXqOTkE7dAXHiPvXVVyuLxw@mail.gmail.com>

Dear Otavio Salvador,

> On Sun, Jun 17, 2012 at 12:43 PM, Stefano Babic <sbabic@denx.de> wrote:
> >> -             return "unknown";
> >> +             return "<unidentified>";
> > 
> > Taste ist taste... but why <unidentified> is better that unknown ?
> 
> For me it gives a visual indication that we didn't meant to support a
> i.MXunknown processor ;-) i.MX<unidentified> make it easy to spot
> this.
> 
> But really, I don't mind it being included or not. I did it because
> Marek has comment about it when looking at my initial mx23 patches.

And I like it more, it looks less like a typo.

Best regards,
Marek Vasut

  reply	other threads:[~2012-06-17 16:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-17 12:58 [U-Boot] [PATCH 0/3] i.MX refactoring patchset Otavio Salvador
2012-06-17 12:58 ` [U-Boot] [PATCH 1/3] imx: Use a clear identification of an unidentified CPU type Otavio Salvador
2012-06-17 13:05   ` Fabio Estevam
2012-06-17 13:09     ` Otavio Salvador
2012-06-17 13:13       ` Fabio Estevam
2012-06-17 13:21         ` Otavio Salvador
2012-06-17 13:30         ` Marek Vasut
2012-06-17 15:43   ` Stefano Babic
2012-06-17 15:48     ` Otavio Salvador
2012-06-17 16:03       ` Marek Vasut [this message]
2012-06-17 17:50         ` Otavio Salvador
2012-06-17 18:04           ` Stefano Babic
2012-06-17 18:40             ` Marek Vasut
2012-06-17 18:04           ` Marek Vasut
2012-06-17 12:58 ` [U-Boot] [PATCH 2/3] mxs: generalize code for print_cpuinfo() Otavio Salvador
2012-06-17 13:10   ` Fabio Estevam
2012-06-17 13:25   ` Fabio Estevam
2012-06-17 13:35     ` Marek Vasut
2012-06-17 14:14       ` Fabio Estevam
2012-06-17 14:35     ` Otavio Salvador
2012-06-17 15:10       ` Marek Vasut
2012-06-17 15:17         ` Otavio Salvador
2012-06-17 13:28   ` Marek Vasut
2012-06-17 15:49   ` Stefano Babic
2012-06-17 16:02     ` Marek Vasut
2012-06-17 17:56       ` Stefano Babic
2012-06-17 18:03         ` Otavio Salvador
2012-06-17 18:41           ` Marek Vasut
2012-06-17 18:04         ` Marek Vasut
2012-06-17 17:49     ` Otavio Salvador
2012-06-17 12:58 ` [U-Boot] [PATCH 3/3] mx28evk: extend default environment Otavio Salvador
2012-06-17 21:54 ` [U-Boot] [PATCH 0/3] i.MX refactoring patchset Marek Vasut

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=201206171803.28260.marex@denx.de \
    --to=marex@denx.de \
    --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