From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: michael@walle.cc, jaimeliao.tw@gmail.com, jaimeliao@mxic.com.tw,
pratyush@kernel.org, richard@nod.at,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: spi-nor: stop printing superfluous debug info
Date: Tue, 28 Nov 2023 08:14:07 +0000 [thread overview]
Message-ID: <e9bbd6a7-3802-4236-9957-6147eb4fd644@linaro.org> (raw)
In-Reply-To: <20231127181514.19b99d2e@xps-13>
On 11/27/23 17:15, Miquel Raynal wrote:
> Hi Tudor,
>
Hi!
> tudor.ambarus@linaro.org wrote on Mon, 27 Nov 2023 16:59:08 +0000:
>
>> The mtd data can be obtain with the mtd ioctls and the SPI NOR
>> flash name can be determined interrogating the sysfs entries.
>> Stop polluting the kernel log.
>
> Actually I like these prints when developing/fixing stuff, it's a clear
> indication of what's been discovered that is available even if for some
> reason my rootfs is not available (which is common when the rootfs is
> on a spi-nor).
>
> So I would not trash all these lines personally... I believe the
What do you find useful about these prints? Maybe you mean that you'd
like some indicator that the SPI NOR probed successfully? How abut
adding a debug message at the end of mtd_device_register(), or otherwise
after mtd_device_register() is called?
> dev_info can be lowered if you prefer, but dev_dbg is already meant for
> debugging purposes and will anyway be discarded by default.
Yes, if we're going to keep these sort of prints I think we should
definitely lower them from info to dbg. It will speed the boot time and
stop polluting the kernel log.
Cheers,
ta
next prev parent reply other threads:[~2023-11-28 8:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 16:59 Tudor Ambarus
2023-11-27 17:15 ` Miquel Raynal
2023-11-28 8:14 ` Tudor Ambarus [this message]
2023-11-28 8:47 ` Michael Walle
2023-11-28 9:03 ` Miquel Raynal
2023-11-28 9:10 ` Michael Walle
2023-11-28 9:24 ` liao jaime
2023-11-28 9:39 ` Tudor Ambarus
2023-11-28 9:47 ` Tudor Ambarus
2023-11-28 11:04 ` Miquel Raynal
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=e9bbd6a7-3802-4236-9957-6147eb4fd644@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=jaimeliao.tw@gmail.com \
--cc=jaimeliao@mxic.com.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
/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
all inboxes | Powered by JetHome®