From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <Tudor.Ambarus@microchip.com>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Vladimir Zapolskiy <vz@mleia.com>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: [PATCH 0/8] Cleanup series about Hamming helpers
Date: Wed, 29 Sep 2021 00:14:59 +0200 [thread overview]
Message-ID: <20210928221507.199198-1-miquel.raynal@bootlin.com> (raw)
Hello,
The detailed description is available in each patch description but
basically:
* The FSMC driver was (I believe) still broken so here is a patch for
that.
* As requested by Linus when he pulled a series of fixes during the 5.13
cycle, the need for declaring individual indentical helpers in each
driver using the "raw" Hamming ECC helpers was unjustified:
- Here is a proposal for simplifying the situation
- Followed by a series of revert (no need to backport these, it's just
general cleanup).
Thanks,
Miquèl
Miquel Raynal (8):
mtd: rawnand: fsmc: Fix use of SM ORDER
mtd: rawnand: Let callers use the bare Hamming helpers
Revert "mtd: rawnand: txx9ndfmc: Fix external use of SW Hamming ECC
helper"
Revert "mtd: rawnand: tmio: Fix external use of SW Hamming ECC helper"
Revert "mtd: rawnand: sharpsl: Fix external use of SW Hamming ECC
helper"
Revert "mtd: rawnand: ndfc: Fix external use of SW Hamming ECC helper"
Revert "mtd: rawnand: lpc32xx_slc: Fix external use of SW Hamming ECC
helper"
Revert "mtd: rawnand: cs553x: Fix external use of SW Hamming ECC
helper"
drivers/mtd/nand/ecc-sw-hamming.c | 7 ++++---
drivers/mtd/nand/raw/cs553x_nand.c | 12 +-----------
drivers/mtd/nand/raw/fsmc_nand.c | 4 +++-
drivers/mtd/nand/raw/lpc32xx_slc.c | 15 +--------------
drivers/mtd/nand/raw/ndfc.c | 12 +-----------
drivers/mtd/nand/raw/sharpsl.c | 12 +-----------
drivers/mtd/nand/raw/tmio_nand.c | 8 +++-----
drivers/mtd/nand/raw/txx9ndfmc.c | 5 ++---
8 files changed, 16 insertions(+), 59 deletions(-)
--
2.27.0
next reply other threads:[~2021-09-28 22:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 22:14 Miquel Raynal [this message]
2021-09-28 22:15 ` [PATCH 1/8] mtd: rawnand: fsmc: Fix use of SM ORDER Miquel Raynal
2021-10-15 10:33 ` Miquel Raynal
2021-09-28 22:15 ` [PATCH 2/8] mtd: rawnand: Let callers use the bare Hamming helpers Miquel Raynal
2021-10-15 10:33 ` Miquel Raynal
2021-09-28 22:15 ` [PATCH 3/8] Revert "mtd: rawnand: txx9ndfmc: Fix external use of SW Hamming ECC helper" Miquel Raynal
2021-10-15 10:33 ` Miquel Raynal
2021-09-28 22:15 ` [PATCH 4/8] Revert "mtd: rawnand: tmio: " Miquel Raynal
2021-10-15 10:33 ` Miquel Raynal
2021-09-28 22:15 ` [PATCH 5/8] Revert "mtd: rawnand: sharpsl: " Miquel Raynal
2021-10-15 10:32 ` Miquel Raynal
2021-09-28 22:15 ` [PATCH 6/8] Revert "mtd: rawnand: ndfc: " Miquel Raynal
2021-10-15 10:32 ` Miquel Raynal
2021-09-28 22:15 ` [PATCH 7/8] Revert "mtd: rawnand: lpc32xx_slc: " Miquel Raynal
2021-10-15 10:32 ` Miquel Raynal
2021-09-28 22:15 ` [PATCH 8/8] Revert "mtd: rawnand: cs553x: " Miquel Raynal
2021-10-15 10:32 ` 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=20210928221507.199198-1-miquel.raynal@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=vz@mleia.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).