All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Cheng Ming Lin <linchengming884@gmail.com>
Cc: vigneshr@ti.com,  linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org,  richard@nod.at,
	 alvinzhou@mxic.com.tw, leoyu@mxic.com.tw,
	 Cheng Ming Lin <chengminglin@mxic.com.tw>
Subject: Re: [PATCH v4 0/2] Add support for read retry
Date: Fri, 21 Feb 2025 14:59:49 +0100	[thread overview]
Message-ID: <87r03rfley.fsf@bootlin.com> (raw)
In-Reply-To: <20250221093300.430994-1-linchengming884@gmail.com> (Cheng Ming Lin's message of "Fri, 21 Feb 2025 17:32:58 +0800")

Hello,

On 21/02/2025 at 17:32:58 +08, Cheng Ming Lin <linchengming884@gmail.com> wrote:

> From: Cheng Ming Lin <chengminglin@mxic.com.tw>
>
> When the host ECC fails to correct the data error of NAND device,
> there's a special read for data recovery method which can be setup
> by the host for the next read. There are several retry levels that
> can be attempted until the lost data is recovered or definitely
> assumed lost.

I am sorry but you need to rebase on latest -rc1 or maybe even nand/next
because it does not apply.

Thanks,
Miquèl

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

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Cheng Ming Lin <linchengming884@gmail.com>
Cc: vigneshr@ti.com,  linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org,  richard@nod.at,
	 alvinzhou@mxic.com.tw, leoyu@mxic.com.tw,
	 Cheng Ming Lin <chengminglin@mxic.com.tw>
Subject: Re: [PATCH v4 0/2] Add support for read retry
Date: Fri, 21 Feb 2025 14:59:49 +0100	[thread overview]
Message-ID: <87r03rfley.fsf@bootlin.com> (raw)
In-Reply-To: <20250221093300.430994-1-linchengming884@gmail.com> (Cheng Ming Lin's message of "Fri, 21 Feb 2025 17:32:58 +0800")

Hello,

On 21/02/2025 at 17:32:58 +08, Cheng Ming Lin <linchengming884@gmail.com> wrote:

> From: Cheng Ming Lin <chengminglin@mxic.com.tw>
>
> When the host ECC fails to correct the data error of NAND device,
> there's a special read for data recovery method which can be setup
> by the host for the next read. There are several retry levels that
> can be attempted until the lost data is recovered or definitely
> assumed lost.

I am sorry but you need to rebase on latest -rc1 or maybe even nand/next
because it does not apply.

Thanks,
Miquèl

  parent reply	other threads:[~2025-02-21 14:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21  9:32 [PATCH v4 0/2] Add support for read retry Cheng Ming Lin
2025-02-21  9:32 ` Cheng Ming Lin
2025-02-21  9:32 ` [PATCH v4 1/2] mtd: spi-nand: Add read retry support Cheng Ming Lin
2025-02-21  9:32   ` Cheng Ming Lin
2025-02-21  9:33 ` [PATCH v4 2/2] mtd: spi-nand: macronix: Add support for read retry Cheng Ming Lin
2025-02-21  9:33   ` Cheng Ming Lin
2025-02-21 13:59 ` Miquel Raynal [this message]
2025-02-21 13:59   ` [PATCH v4 0/2] " 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=87r03rfley.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=alvinzhou@mxic.com.tw \
    --cc=chengminglin@mxic.com.tw \
    --cc=leoyu@mxic.com.tw \
    --cc=linchengming884@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.