From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Miquel Raynal <miquel.raynal@free-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH v3 0/7] Marvell NAND controller rework with ->exec_op()
Date: Mon, 22 Jan 2018 09:51:49 +0100 [thread overview]
Message-ID: <20180122095149.590612d9@bbrezillon> (raw)
In-Reply-To: <87o9lwaft9.fsf@belgarion.home>
Hi Robert,
On Sun, 14 Jan 2018 11:35:30 +0100
Robert Jarzmik <robert.jarzmik@free.fr> wrote:
> Miquel Raynal <miquel.raynal@free-electrons.com> writes:
>
> >> It shouldn't be damaged anymore. The bug has been fixed just before we
> >> asked you to scrub the BBT area.
> I confirm. The last marvell branch I have (2be03e113a5b ("HACK: Dump OOB data
> while reading")) does work correctly on my zylonite.
>
> I still have to make a test of a file write, and a devicetree based setup, but I
> don't think anything wrong will happen now.
Did you make any progress with that? Note that, no matter the outcome
of your tests, I don't plan to queue the remaining patches for this
release, so don't be afraid of putting your Tested-by/Acked-by on
patches 5-6 if it works on your platforms ;-).
Thanks,
Boris
next prev parent reply other threads:[~2018-01-22 8:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 10:36 [PATCH v3 0/7] Marvell NAND controller rework with ->exec_op() Miquel Raynal
2018-01-09 10:36 ` [PATCH v3 1/7] dt-bindings: mtd: document new nand-rb property Miquel Raynal
2018-01-11 22:23 ` Rob Herring
2018-01-09 10:36 ` [PATCH v3 2/7] dt-bindings: mtd: add Marvell NAND controller documentation Miquel Raynal
2018-01-11 22:25 ` Rob Herring
2018-01-09 10:36 ` [PATCH v3 3/7] mtd: nand: add reworked Marvell NAND controller driver Miquel Raynal
2018-01-09 10:36 ` [PATCH v3 4/7] mtd: nand: use reworked NAND controller driver with Marvell EBU SoCs Miquel Raynal
2018-01-09 10:36 ` [PATCH v3 5/7] mtd: nand: use Marvell reworked NAND controller driver with all platforms Miquel Raynal
2018-02-12 10:20 ` Boris Brezillon
2018-01-09 10:36 ` [PATCH v3 6/7] dt-bindings: mtd: remove pxa3xx NAND controller documentation Miquel Raynal
2018-01-09 10:36 ` [PATCH v3 7/7] mtd: nand: remove useless fields from pxa3xx NAND platform data Miquel Raynal
2018-02-12 10:17 ` Miquel Raynal
2018-02-17 9:43 ` Robert Jarzmik
2018-01-11 11:27 ` [PATCH v3 0/7] Marvell NAND controller rework with ->exec_op() Boris Brezillon
2018-01-11 17:42 ` Robert Jarzmik
2018-01-11 22:24 ` Miquel RAYNAL
2018-01-12 8:09 ` Robert Jarzmik
2018-01-12 8:45 ` Boris Brezillon
2018-01-12 9:01 ` Miquel Raynal
2018-01-12 9:34 ` Robert Jarzmik
2018-01-12 9:52 ` Boris Brezillon
2018-01-12 20:44 ` Robert Jarzmik
2018-01-13 8:38 ` Boris Brezillon
2018-01-13 11:05 ` Miquel Raynal
2018-01-14 10:35 ` Robert Jarzmik
2018-01-22 8:51 ` Boris Brezillon [this message]
2018-01-27 10:33 ` Robert Jarzmik
2018-01-29 10:36 ` Boris Brezillon
2018-01-12 10:21 ` Boris Brezillon
2018-01-12 16:43 ` Robert Jarzmik
2018-01-13 8:38 ` Boris Brezillon
2018-01-14 10:20 ` Robert Jarzmik
2018-01-22 8:54 ` Boris Brezillon
2018-01-11 22:28 ` Willy Tarreau
2018-01-12 18:21 ` Miquel Raynal
2018-01-12 15:55 ` 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=20180122095149.590612d9@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@free-electrons.com \
--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