From: Brian Norris <computersforpeace@gmail.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: Stefan Roese <sr@denx.de>,
linux-mtd <linux-mtd@lists.infradead.org>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Subject: Re: [PATCH v2] mtd: nand: omap: fix BCHx ecc.correct to return detected bit-flips in erased-page
Date: Tue, 20 May 2014 16:42:49 -0700 [thread overview]
Message-ID: <20140520234249.GZ28907@ld-irv-0074> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73EACE4A3@DBDE04.ent.ti.com>
On Tue, May 20, 2014 at 04:43:35AM +0000, Pekon Gupta wrote:
> This fix is really important to be marked as stable, as some users of OMAP
> platforms have spawning out from 3.10 and 3.12 kernel to go for production.
> And quite a few of them might be using NAND for their booting purpose,
> so without this patch any bit-flip on their erased-pages will not be detected.
Well, I don't think it's actually as dire as you say. The erased-page
bitflips won't be flagged as -EUCLEAN, but they will be "corrected." I
expect that this should be fine mostly.
But anyway, tagged for -stable and re-queued to l2-mtd.git.
In the future, I may be less likely to do this kind of rebasing. Note
that there is still a procedure for getting fixes to -stable after their
merging:
<quote>
- Send the patch, after verifying that it follows the above rules, to
stable@vger.kernel.org. You must note the upstream commit ID in the
changelog of your submission, as well as the kernel version you wish
it to be applied to.
</quote>
Brian
next prev parent reply other threads:[~2014-05-20 23:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 6:58 [PATCH v2] mtd: nand: omap: fix BCHx ecc.correct to return detected bit-flips in erased-page Pekon Gupta
2014-03-25 7:05 ` Gupta, Pekon
2014-04-23 6:29 ` Gupta, Pekon
2014-05-12 20:36 ` Brian Norris
2014-05-19 5:00 ` Gupta, Pekon
2014-05-19 12:20 ` Ezequiel Garcia
2014-05-20 4:43 ` Gupta, Pekon
2014-05-20 23:42 ` Brian Norris [this message]
2014-05-22 17:56 ` Gupta, Pekon
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=20140520234249.GZ28907@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=linux-mtd@lists.infradead.org \
--cc=pekon@ti.com \
--cc=sr@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