public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	 linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] mtd: spi-nor: simplify spi_nor_get_flash_info()
Date: Tue, 18 Jun 2024 11:46:54 +0200	[thread overview]
Message-ID: <mafs08qz2fur5.fsf@kernel.org> (raw)
In-Reply-To: <20240603134055.1859863-1-mwalle@kernel.org> (Michael Walle's message of "Mon, 3 Jun 2024 15:40:55 +0200")

Hi Michael,

On Mon, Jun 03 2024, Michael Walle wrote:

> Rework spi_nor_get_flash_info() to make it look more straight forward
> and esp. don't return early. The latter is a preparation to check for
> deprecated flashes.
>
> Signed-off-by: Michael Walle <mwalle@kernel.org>

Reviewed-by: Pratyush Yadav <pratyush@kernel.org>

Applied to spi-nor/next. Thanks.

> ---
> v3:
>  - rework the handling quite a bit, thanks Tudor.
>  - drop the spurious comment about the partitions, it goes way back
>    until the initial support. I don't think it's accurate anymore.
>    If the flash has the same size, the partitions can be trusted. If
>    not, anything can happen.. We don't know.
>
> v2/v1:
>  - none, this is a remaining patch of my spring cleanup series.

Do you also plan to re-roll the deprecation patch some time in the
future?

-- 
Regards,
Pratyush Yadav

      reply	other threads:[~2024-06-18  9:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 13:40 [PATCH v3] mtd: spi-nor: simplify spi_nor_get_flash_info() Michael Walle
2024-06-18  9:46 ` 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=mafs08qz2fur5.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=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