From: "Michael Walle" <mwalle@kernel.org>
To: "Miquel Raynal" <miquel.raynal@bootlin.com>,
"Sean Anderson" <sean.anderson@linux.dev>
Cc: "Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Pratyush Yadav" <pratyush@kernel.org>,
<linux-mtd@lists.infradead.org>,
"Richard Weinberger" <richard@nod.at>,
<linux-kernel@vger.kernel.org>,
"Vignesh Raghavendra" <vigneshr@ti.com>
Subject: Re: [PATCH] mtd: spi-nor: Enable locking for n25q00a
Date: Wed, 12 Nov 2025 14:34:20 +0100 [thread overview]
Message-ID: <DE6R76H9N8H0.NKHN0YUTE8LL@kernel.org> (raw)
In-Reply-To: <87v7jfgzfw.fsf@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
On Wed Nov 12, 2025 at 2:20 PM CET, Miquel Raynal wrote:
> I forgot to mention: I don't like this interface because it is not very
> user friendly, but this is uAPI, so set in stone. As part of my journey
> in the SPI NOR swp.c file, I wrote a debugfs interface to help
> visualizing what is actually locked. It is absolutely trivial to do and
> helps a lot. We might want to use that for writing some kind of testing
> procedure — I will share it soon.
Yes please, that sounds very good. We might also want to just raw
dump the SR (and maybe CR/SR2 if we somehow can infer it's
existence).
-michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
next prev parent reply other threads:[~2025-11-12 13:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 22:34 [PATCH] mtd: spi-nor: Enable locking for n25q00a Sean Anderson
2025-10-06 22:38 ` Sean Anderson
2025-10-08 5:05 ` Tudor Ambarus
2025-10-08 12:38 ` Pratyush Yadav
2025-10-07 13:15 ` Pratyush Yadav
2025-10-07 14:20 ` Sean Anderson
2025-10-08 12:30 ` Pratyush Yadav
2025-10-08 12:40 ` Pratyush Yadav
2025-10-09 22:27 ` Sean Anderson
2025-10-09 23:07 ` Pratyush Yadav
2025-10-10 15:45 ` Sean Anderson
2025-10-13 7:30 ` Tudor Ambarus
2025-10-14 18:25 ` Sean Anderson
2025-11-10 7:08 ` Tudor Ambarus
2025-11-10 10:16 ` Pratyush Yadav
2025-11-10 16:36 ` Sean Anderson
2025-11-11 6:07 ` Tudor Ambarus
2025-11-12 13:10 ` Miquel Raynal
2025-11-12 13:20 ` Miquel Raynal
2025-11-12 13:34 ` Michael Walle [this message]
2025-11-13 15:32 ` Sean Anderson
2025-11-14 17:55 ` 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=DE6R76H9N8H0.NKHN0YUTE8LL@kernel.org \
--to=mwalle@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=sean.anderson@linux.dev \
--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