From: Richard Weinberger <richard@nod.at>
To: Fabio Estevam <festevam@gmail.com>,
Brian Norris <computersforpeace@gmail.com>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Huang Shijie <shijie8@gmail.com>
Subject: Re: [PATCH] mtd: gpmi: Remove noisy error message
Date: Wed, 26 Nov 2014 14:35:15 +0100 [thread overview]
Message-ID: <5475D713.9050101@nod.at> (raw)
In-Reply-To: <CAOMZO5C_9er34oqGCYWfhe3NvmJXfqC21s_Uiset7_y7NKHXXA@mail.gmail.com>
Am 26.11.2014 um 12:44 schrieb Fabio Estevam:
> On Wed, Nov 26, 2014 at 1:18 AM, Brian Norris
> <computersforpeace@gmail.com> wrote:
>> On Tue, Nov 11, 2014 at 06:16:29PM -0200, Fabio Estevam wrote:
>>> BTW, I don't see any other nand driver that prints error on the probe
>>> error path like this one.
>>
>> You're probably still going to see failure prints like
>>
>> nand: No NAND device found
>>
>> in nand_scan_ident(), right? Or does driver probe fail earlier than that
>> somehow?
>
> Yes, this is what I get currently:
>
> [ 1.645433] nand: No NAND device found
> [ 1.650372] gpmi-nand 8000c000.gpmi-nand: driver registration failed: -19
>
> In my opinion the "No NAND device found" is enough.
If we remove the said log message and one really has a NAND installed which fails
to probe will he notice that and get the correct error code printed?
If yes, the removal won't hurt.
My point is that having non-existing hardware in the device does not make much sense.
Lot's of DTs are very generic and carry a lot of unused stuff with them,
but this is not a good practice as DTs should describe the actual hardware and not
all possible board variants.
Thanks,
//richard
next prev parent reply other threads:[~2014-11-26 13:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 16:01 [PATCH] mtd: gpmi: Remove noisy error message Fabio Estevam
2014-11-11 19:45 ` Richard Weinberger
2014-11-11 19:57 ` Fabio Estevam
2014-11-11 20:00 ` Richard Weinberger
2014-11-11 20:05 ` Fabio Estevam
2014-11-11 20:10 ` Richard Weinberger
2014-11-11 20:16 ` Fabio Estevam
2014-11-11 20:22 ` Richard Weinberger
2014-11-11 20:28 ` Fabio Estevam
2014-11-11 20:31 ` Richard Weinberger
2014-11-26 3:18 ` Brian Norris
2014-11-26 11:44 ` Fabio Estevam
2014-11-26 13:35 ` Richard Weinberger [this message]
2014-12-17 0:27 ` Brian Norris
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=5475D713.9050101@nod.at \
--to=richard@nod.at \
--cc=computersforpeace@gmail.com \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=shijie8@gmail.com \
/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.