All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mx51: Print silicon revision on boot
Date: Thu, 03 Mar 2011 19:12:25 +0100	[thread overview]
Message-ID: <87d3m8vzsm.fsf@lebrac.rtp-net.org> (raw)
In-Reply-To: <20110303164427.GX29521@pengutronix.de> (Sascha Hauer's message of "Thu, 3 Mar 2011 17:44:27 +0100")

Sascha Hauer <s.hauer@pengutronix.de> writes:

Hi,

> On Thu, Mar 03, 2011 at 12:43:14PM -0300, Fabio Estevam wrote:
>> Hi Arnaud,
>> 
>> On Thu, Mar 3, 2011 at 5:24 AM, Arnaud Patard <arnaud.patard@rtp-net.org> wrote:
>> > Fabio Estevam <festevam@gmail.com> writes:
>> > Hi,
>> >
>> >> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
>> >
>> > Why I like having boot log, I don't like have too verbose boot logs. If
>> > you add this, you have a good reason (I hope), but I can't know
>> > it. There's no patch description. So, please give a patch with proper
>> > explanation of why you need that. Anyway, having a proper patch
>> > description is imho always a good idea.
>> 
>> I think that printing the silicon version on boot is useful
>> information. Many issues are fixed in the latest silicon revision, so
>> while debugging mx51 issues it is good to know from the boot log if
>> someone is using the latest silicon version or not.
>
> +1
>
> There is less useful information in the bootlog than this. Also, there's
> the quiet option to not wait on the slow serial console.

You missed something in my mail. My point was not really about log
verbosity. There was *no* description at all. We both know that silicon
rev 2.0 has some nasty bugs like broken neon which has been fixed in rev
3.0 so it may be a good idea to print that but without proper
description, the aim may well have been "I want to print this because I
find it nice". I know it may be hard to write proper description but
here, it's not. I even got a good description as answer to my mail. I
should not had to ask for it.

Arnaud

  reply	other threads:[~2011-03-03 18:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-03  1:12 [PATCH] ARM: mx51: Print silicon revision on boot Fabio Estevam
2011-03-03  8:24 ` Arnaud Patard (Rtp)
2011-03-03 15:43   ` Fabio Estevam
2011-03-03 16:44     ` Sascha Hauer
2011-03-03 18:12       ` Arnaud Patard (Rtp) [this message]
2011-03-03 18:22         ` Sascha Hauer

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=87d3m8vzsm.fsf@lebrac.rtp-net.org \
    --to=arnaud.patard@rtp-net.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.