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 20:40:44 +0200 [thread overview]
Message-ID: <201206172040.44376.marex@denx.de> (raw)
In-Reply-To: <4FDE1C28.8030605@denx.de>
Dear Stefano Babic,
> On 17/06/2012 19:50, Otavio Salvador wrote:
> > On Sun, Jun 17, 2012 at 1:03 PM, Marek Vasut <marex@denx.de> wrote:
> >>> 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.
> >
> > Sorry; I didn't get what you meant ... should it go or not?
>
> Hi Otavio,
>
> I make also my point clearer for Marek: my point is that the behavior
> for all i.MX must be consistent. If you change here, please change also
> for i.MX31 (that returns "unknown in print_cpuinfo) and for other SOCs
> that returns "unknown" in print_cpuinfo() - or let the code as now.
Ah, I thought it was about the revision. Ok, whatever way is fine by me.
> Best regards,
> Stefano
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-06-17 18:40 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
2012-06-17 17:50 ` Otavio Salvador
2012-06-17 18:04 ` Stefano Babic
2012-06-17 18:40 ` Marek Vasut [this message]
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=201206172040.44376.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