From: Ladislav Michl <ladis@linux-mips.org>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Richard Weinberger <richard@nod.at>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
linux-mtd@lists.infradead.org,
Robert Jarzmik <robert.jarzmik@free.fr>,
Kyungmin Park <kyungmin.park@samsung.com>,
Peter Pan <peterpansjtu@gmail.com>,
Frieder Schrempf <frieder.schrempf@exceet.de>,
Miquel RAYNAL <miquel.raynal@free-electrons.com>
Subject: Re: [PATCH v4 0/4] mtd: Preparation patches for the SPI NAND framework
Date: Mon, 8 Jan 2018 22:48:19 +0100 [thread overview]
Message-ID: <20180108214819.GA16174@lenoch> (raw)
In-Reply-To: <20180108211542.11891-1-boris.brezillon@free-electrons.com>
On Mon, Jan 08, 2018 at 10:15:39PM +0100, Boris Brezillon wrote:
> Hello,
>
> Here is a set of patches preparing the introduction of the generic
> NAND and SPI frameworks.
Tested on IGEPv2 Rev. B (TI OMAP3530) with Muxed OneNAND(DDP) 512MB 1.8V
16-bit (0x58) after fixing PATCH v4 1/3.
Tested-by: Ladislav Michl <ladis@linux-mips.org>
> If you want to see the overall picture of the SPI NAND framework you can
> have a look at this branch [2].
>
> Regards,
>
> Boris
>
> Change in v4:
> - add "mtd: mtdpart: Make ECC stat handling consistent" and
> - integrate "mtd: Remove duplicate checks on mtd_oob_ops parameter"
> into this series
> - drop "mtd: Stop directly calling master ->_xxx() hooks from mtdpart
> code"
>
> Boris Brezillon (3):
> mtd: mtdpart: Make ECC stat handling consistent
> mtd: Fallback to ->_read/write_oob() when ->_read/write() is missing
> mtd: Remove duplicate checks on mtd_oob_ops parameter
>
> drivers/mtd/devices/docg3.c | 70 ------------------------------
> drivers/mtd/mtdcore.c | 31 +++++++++++++-
> drivers/mtd/mtdpart.c | 42 +++++-------------
> drivers/mtd/nand/nand_base.c | 87 --------------------------------------
> drivers/mtd/onenand/onenand_base.c | 81 -----------------------------------
> 5 files changed, 40 insertions(+), 271 deletions(-)
>
> --
> 2.11.0
prev parent reply other threads:[~2018-01-08 21:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 21:15 [PATCH v4 0/4] mtd: Preparation patches for the SPI NAND framework Boris Brezillon
2018-01-08 21:15 ` [PATCH v4 1/3] mtd: mtdpart: Make ECC stat handling consistent Boris Brezillon
2018-01-08 21:25 ` Boris Brezillon
2018-01-10 20:27 ` Robert Jarzmik
2018-01-10 21:07 ` Boris Brezillon
2018-01-08 21:15 ` [PATCH v4 2/3] mtd: Fallback to ->_read/write_oob() when ->_read/write() is missing Boris Brezillon
2018-01-08 21:15 ` [PATCH v4 3/3] mtd: Remove duplicate checks on mtd_oob_ops parameter Boris Brezillon
2018-01-08 22:04 ` Miquel RAYNAL
2018-01-08 22:30 ` Boris Brezillon
2018-01-09 7:19 ` Miquel RAYNAL
2018-01-09 8:11 ` Boris Brezillon
2018-01-09 8:19 ` Miquel RAYNAL
2018-01-08 21:17 ` [PATCH v4 0/4] mtd: Preparation patches for the SPI NAND framework Boris Brezillon
2018-01-08 21:48 ` Ladislav Michl [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=20180108214819.GA16174@lenoch \
--to=ladis@linux-mips.org \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=frieder.schrempf@exceet.de \
--cc=kyungmin.park@samsung.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@free-electrons.com \
--cc=peterpansjtu@gmail.com \
--cc=richard@nod.at \
--cc=robert.jarzmik@free.fr \
/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).