From: RogerCC.Lin <rogercc.lin@mediatek.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: <xiaolei.li@mediatek.com>, <steven.liu@mediatek.com>,
<robh@kernel.org>, <computersforpeace@gmail.com>,
<daniel.thompson@linaro.org>, <linux-mtd@lists.infradead.org>,
<matthias.bgg@gmail.com>, <linux-mediatek@lists.infradead.org>,
<dwmw2@infradead.org>, <blogic@openwrt.org>,
Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
Subject: [PATCH v2 0/2] mtd: nand: fix writing incorrect ECC parity data in OOB region.
Date: Mon, 29 Aug 2016 19:40:03 +0800 [thread overview]
Message-ID: <1472470803.11041.4.camel@mtkswgap22> (raw)
In-Reply-To: <20160829101006.2b200e0a@bbrezillon>
This series fix chances to write incorrect ECC data which may cause
uncorrectable ECC error when reading.
changes since v1:
- separate patches into 2.
- use shift operator with byte access to avoid endianness conversion
problems.
- follow linux coding style.
The patch passed the test of UBIFS file-system read/write on Mediatek's
RFB. The tested driver is checked-out from LEDE OpenWRT project's
upstream driver, which is pretty much same as nand/next branch upstream
driver(git clone https://git.lede-project.org/source.git).
RogerCC Lin (2):
mtd: nand: fix generating over-boundary ECC data when writing.
mtd: nand: fix chances to create incomplete ECC data when writing.
drivers/mtd/nand/mtk_ecc.c | 12 ++++++++----
drivers/mtd/nand/mtk_nand.c | 8 ++++----
2 files changed, 12 insertions(+), 8 deletions(-)
next prev parent reply other threads:[~2016-08-29 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 3:58 [Patch] mtd: fix writing incorrect ECC parity data in OOB region mtk04561
2016-08-29 8:10 ` Boris Brezillon
2016-08-29 8:56 ` Jorge Ramirez
2016-08-29 11:40 ` RogerCC.Lin [this message]
2016-08-29 11:53 ` [PATCH v2 0/2] mtd: nand: " RogerCC.Lin
2016-08-29 11:40 ` [PATCH v2 1/2] mtd: nand: fix generating over-boundary ECC data when writing RogerCC.Lin
2016-08-29 11:40 ` [PATCH v2 2/2] mtd: nand: fix chances to create incomplete " RogerCC.Lin
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=1472470803.11041.4.camel@mtkswgap22 \
--to=rogercc.lin@mediatek.com \
--cc=blogic@openwrt.org \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=daniel.thompson@linaro.org \
--cc=dwmw2@infradead.org \
--cc=jorge.ramirez-ortiz@linaro.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=steven.liu@mediatek.com \
--cc=xiaolei.li@mediatek.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