From: Pratyush Yadav <pratyush@kernel.org>
To: Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: Sean Anderson <sean.anderson@linux.dev>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <mwalle@kernel.org>,
linux-mtd@lists.infradead.org,
Richard Weinberger <richard@nod.at>,
linux-kernel@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH] mtd: spi-nor: Enable locking for n25q00a
Date: Mon, 10 Nov 2025 11:16:11 +0100 [thread overview]
Message-ID: <mafs0v7ji9or8.fsf@kernel.org> (raw)
In-Reply-To: <31d01667-e80e-423c-bdab-8d05831d575d@linaro.org> (Tudor Ambarus's message of "Mon, 10 Nov 2025 09:08:07 +0200")
On Mon, Nov 10 2025, Tudor Ambarus wrote:
> The locking tests look fine to me:
>
> Acked-by: Tudor Ambarus <tudor.ambarus@linaro.org>
Thanks for reviewing Tudor.
I would like a re-roll with the commit message updated before applying
this.
>
> Sean, if you care you can extend the documentation on how to test locking.
> Also, you may drop the non SFDP data from the flash's static definition as
> a follow up patch.
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2025-11-10 10:16 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 [this message]
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
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=mafs0v7ji9or8.fsf@kernel.org \
--to=pratyush@kernel.org \
--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=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