From: RogerCC Lin <rogercc.lin@mediatek.com>
To: <boris.brezillon@free-electrons.com>
Cc: <xiaolei.li@mediatek.com>, <steven.liu@mediatek.com>,
<robh@kernel.org>, <computersforpeace@gmail.com>,
<jorge.ramirez-ortiz@linaro.org>, <daniel.thompson@linaro.org>,
<linux-mtd@lists.infradead.org>, <matthias.bgg@gmail.com>,
<srv_heupstream@mediatek.com>,
<linux-mediatek@lists.infradead.org>, <dwmw2@infradead.org>,
<blogic@openwrt.org>, RogerCC Lin <rogercc.lin@mediatek.com>
Subject: [PATCH v4 0/2] mtd: nand: fix writing incorrect ECC parity data in OOB region
Date: Tue, 30 Aug 2016 20:35:46 +0800 [thread overview]
Message-ID: <1472560548-30567-1-git-send-email-rogercc.lin@mediatek.com> (raw)
From: RogerCC Lin <rogercc.lin@mediatek.com>
This series fix chances to write incorrect ECC data which may cause uncorrectable ECC error when reading.
changes since v3:
- use macro for function arguments.
changes since v2:
- use macro for shift operation.
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 | 7 +++++--
2 files changed, 13 insertions(+), 6 deletions(-)
next reply other threads:[~2016-08-30 12:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 12:35 RogerCC Lin [this message]
2016-08-30 12:35 ` [PATCH v4 1/2] mtd: nand: fix generating over-boundary ECC data when writing RogerCC Lin
2016-08-31 8:09 ` Boris Brezillon
2016-08-31 8:19 ` RogerCC.Lin
2016-09-15 16:20 ` Boris Brezillon
2016-08-30 12:35 ` [PATCH v4 2/2] mtd: nand: fix chances to create incomplete " RogerCC Lin
2016-09-15 16:20 ` Boris Brezillon
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=1472560548-30567-1-git-send-email-rogercc.lin@mediatek.com \
--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=srv_heupstream@mediatek.com \
--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;
as well as URLs for NNTP newsgroup(s).