From: Pratyush Yadav <pratyush@kernel.org>
To: Michael Walle <mwalle@kernel.org>
Cc: Tudor Ambarus <tudor.ambarus@linaro.org>,
Pratyush Yadav <pratyush@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Takahiro Kuwano <Takahiro.Kuwano@infineon.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [PATCH] mtd: spi-nor: fix flash probing
Date: Mon, 09 Sep 2024 15:47:37 +0200 [thread overview]
Message-ID: <mafs04j6pgcqu.fsf@kernel.org> (raw)
In-Reply-To: <20240909072854.812206-1-mwalle@kernel.org> (Michael Walle's message of "Mon, 9 Sep 2024 09:28:54 +0200")
Hi Michael,
Thanks for the quick fix!
On Mon, Sep 09 2024, Michael Walle wrote:
> Fix flash probing by name. Flash entries without a name are allowed
> since commit 15eb8303bb42 ("mtd: spi-nor: mark the flash name as
> obsolete"). But it was just until recently that a flash entry without a
> name was actually introduced. This triggers a bug in the legacy probe by
> name path. Skip entries without a name to fix it.
We also use name in a couple other places:
1. spi_nor_get_flash_info() prints jinfo->name and info->name() in the
dev_warn() call.
2. spi_nor_params_show() prints nor->info->name for the debugfs entry.
Since both of these are prints, it should probably be fine since they
should be converted to "(null)" instead. Still, something we should fix.
I don't think those are critical so those can be fixed as follow up
patches. I unfortunately am swamped and don't have the time to fix them
right now.
I also did a quick check to make sure we don't have other flashes
without a name.
Reviewed-by: Pratyush Yadav <pratyush@kernel.org>
Applied to spi-nor/next. Thanks!
>
> Fixes: 2095e7da8049 ("mtd: spi-nor: spansion: Add support for S28HS256T")
> Reported-by: Jon Hunter <jonathanh@nvidia.com>
> Closes: https://lore.kernel.org/r/66c8ebb0-1324-4ad9-9926-8d4eb7e1e63a@nvidia.com/
> Tested-by: Jon Hunter <jonathanh@nvidia.com>
> Signed-off-by: Michael Walle <mwalle@kernel.org>
[...]
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2024-09-09 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 7:28 [PATCH] mtd: spi-nor: fix flash probing Michael Walle
2024-09-09 7:35 ` Tudor Ambarus
2024-09-09 7:52 ` Miquel Raynal
2024-09-09 8:08 ` Tudor Ambarus
2024-09-09 8:47 ` Miquel Raynal
2024-09-09 13:52 ` Pratyush Yadav
2024-09-09 13:47 ` Pratyush Yadav [this message]
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=mafs04j6pgcqu.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=Takahiro.Kuwano@infineon.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=richard@nod.at \
--cc=tudor.ambarus@linaro.org \
--cc=vigneshr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox