Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Jakub Czapiga <czapiga@google.com>
Cc: Pratyush Yadav <pratyush@kernel.org>,
	Michael Walle <mwalle@kernel.org>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: spi-nor: eon: fix lock and non-SFDP flags
Date: Tue, 18 Mar 2025 09:12:32 +0200	[thread overview]
Message-ID: <47905b67-c0b5-45c9-98e2-0dc4dcf9651e@linaro.org> (raw)
In-Reply-To: <20250317181856.2059536-1-czapiga@google.com>



On 17.03.2025 20:18, Jakub Czapiga wrote:
> Set appropriate FLASH lock feature flags for chips that support it.
> Set top-bottom protection bit flag for chips that support it.
> Add no-SFDP flags for chips with missing SFDP or without clear
> SFDP description regarding 4K sectors, dual and quad read support.
> Remove no-SFDP flags for chips which documentation states that this
> information can be extracted from SFDP.

Patches per flash please. Then dedicated patch for each logical change.
With testing.

Thanks,
ta

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

      reply	other threads:[~2025-03-18  7:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17 18:18 [PATCH] mtd: spi-nor: eon: fix lock and non-SFDP flags Jakub Czapiga
2025-03-18  7:12 ` Tudor Ambarus [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=47905b67-c0b5-45c9-98e2-0dc4dcf9651e@linaro.org \
    --to=tudor.ambarus@linaro.org \
    --cc=czapiga@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=mwalle@kernel.org \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --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