mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Roland Hieber <r.hieber@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 1/2] drivers: caam: add RNG software self-test
Date: Tue, 4 Dec 2018 08:49:58 +0100	[thread overview]
Message-ID: <20181204074958.x6bntw4czthc75ye@pengutronix.de> (raw)
In-Reply-To: <20181203105226.tk633gpq3w2hsdbl@pengutronix.de>

On Mon, Dec 03, 2018 at 11:52:26AM +0100, Roland Hieber wrote:
> Hi Sascha,
> 
> > +	pr_notice("RNG software self-test passed\n");
> 
> I noticed that you downgraded this to a pr_info() when applying the
> patch, is there a reason?  pr_warn()s have the "WARNING:" prefix,
> pr_notice()s have a "NOTICE:" prefix, but pr_info()s don't have any
> prefix. I think this one should be a pr_notice because it overrides the
> pr_warn("RNG self-test failure detected...") from HAB and tells the user
> that this warning is no longer relevant. With pr_info(), I think it will
> get lost between all the other infos.

I can follow this argumentation, but then I argue we should lower the
priority of the failure detected message to to pr_info or even pr_debug,
because the failure is pretty much expected, it is correctly being
worked around and there's nothing we can do about the failure.

People tend to bother about warnings and ask questions what is wrong.
When everything you can do is to tell that everything is fine then probably
the warning shouldn't be there in the first place.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2018-12-04  7:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-29 13:42 Roland Hieber
2018-11-29 13:42 ` [PATCH v2 2/2] i.MX: HABv4: always print HAB status at boot time Roland Hieber
2018-12-03  8:01 ` [PATCH v2 1/2] drivers: caam: add RNG software self-test Sascha Hauer
2018-12-03 10:15   ` [PATCH] fixup! " Roland Hieber
2018-12-04  7:31     ` Sascha Hauer
2018-12-03 10:52 ` [PATCH v2 1/2] " Roland Hieber
2018-12-04  7:49   ` Sascha Hauer [this message]
2018-12-04  8:20     ` [PATCH] fixup! " Roland Hieber

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=20181204074958.x6bntw4czthc75ye@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=r.hieber@pengutronix.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