From: Tom Rini <trini@konsulko.com>
To: Joel Peshkin <joel.peshkin@broadcom.com>
Cc: u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH] BRCMNAND: Fix reporting of uncorrectable errors on subpages during page read
Date: Sat, 15 Jan 2022 07:38:15 -0500 [thread overview]
Message-ID: <20220115123815.GC9207@bill-the-cat> (raw)
In-Reply-To: <20211221041547.52964-1-joel.peshkin@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 411 bytes --]
On Mon, Dec 20, 2021 at 08:15:47PM -0800, Joel Peshkin wrote:
> Previously, a subpage with an uncorrectable error followed by a subpage
> with a correctable error would return an erroneous correctable status.
>
> Signed-off-by: Joel Peshkin <joel.peshkin@broadcom.com>
> Cc: Simon Glass <sjg@chromium.org>
> Reviewed-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-01-15 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 4:15 [PATCH] BRCMNAND: Fix reporting of uncorrectable errors on subpages during page read Joel Peshkin
2021-12-28 8:33 ` Simon Glass
2022-01-15 12:38 ` Tom Rini [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=20220115123815.GC9207@bill-the-cat \
--to=trini@konsulko.com \
--cc=joel.peshkin@broadcom.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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