From: Boris Brezillon <boris.brezillon@bootlin.com>
To: IKEGAMI Tokunori <ikegami@allied-telesis.co.jp>
Cc: "boris.brezillon@free-electrons.com"
<boris.brezillon@free-electrons.com>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"richard@nod.at" <richard@nod.at>,
Joakim Tjernlund <Joakim.Tjernlund@infinera.com>,
"PACKHAM Chris" <chris.packham@alliedtelesis.co.nz>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"cyrille.pitchen@wedev4u.fr" <cyrille.pitchen@wedev4u.fr>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>
Subject: Re: [PATCH v5 0/2] mtd: cfi_cmdset_0002: Changes to retry for flash erase
Date: Mon, 14 May 2018 09:12:14 +0200 [thread overview]
Message-ID: <20180514091214.35ec45b8@bbrezillon> (raw)
In-Reply-To: <TY1PR01MB09547A5F4FCDAA1FFB601C74DC9C0@TY1PR01MB0954.jpnprd01.prod.outlook.com>
On Mon, 14 May 2018 02:11:48 +0000
IKEGAMI Tokunori <ikegami@allied-telesis.co.jp> wrote:
> From: Tokunori Ikegami <ikegami@allied-telesis.co.jp>
>
> The flash erase error is caused on the Macronix flash device below.
> MX29GL512FHT2I-11G
> Also it has been just confirmed to be able to reproduce.
> And the retry function can resolved the flash erase error correctly.
>
> The commit message of PATCH v4 2/2 was not correct so let me resend patches.
Can you please use git send-email when you send your patch series, so
that they are properly threaded.
>
> Tokunori Ikegami (2):
> mtd: cfi_cmdset_0002: Change definition naming to retry write
> operation
> mtd: cfi_cmdset_0002: Change erase functions to retry for error
>
> drivers/mtd/chips/cfi_cmdset_0002.c | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
next prev parent reply other threads:[~2018-05-14 7:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 2:11 [PATCH v5 0/2] mtd: cfi_cmdset_0002: Changes to retry for flash erase IKEGAMI Tokunori
2018-05-14 7:12 ` Boris Brezillon [this message]
2018-05-14 9:32 ` IKEGAMI Tokunori
2018-05-14 9:44 ` Boris Brezillon
2018-05-14 10:23 ` IKEGAMI Tokunori
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=20180514091214.35ec45b8@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=Joakim.Tjernlund@infinera.com \
--cc=boris.brezillon@free-electrons.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=ikegami@allied-telesis.co.jp \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
/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