linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Tudor Ambarus <Tudor.Ambarus@microchip.com>,
	linux-mtd@lists.infradead.org
Cc: Zoltan Szubbocsev <zszubbocsev@micron.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Boris Brezillon <boris.brezillon@collabora.com>,
	tglx@linutronix.de,
	Piotr Wojtaszczyk <WojtaszczykP@cumminsallison.com>,
	Bean Huo <beanhuo@micron.com>
Subject: Re: [RFC PATCH 0/3] Fix proposal for the Micron shallow erase issue
Date: Thu, 2 Jan 2020 10:41:14 -0800	[thread overview]
Message-ID: <a2199251-882a-5067-fe4c-47f1c8a252fe@gmail.com> (raw)
In-Reply-To: <20191231192656.16376-1-miquel.raynal@bootlin.com>

On 12/31/19 11:26 AM, Miquel Raynal wrote:
> Hello,
> 
> After a first proposal by Thomas Gleixner and then another proposal by
> Bean Huo (Micron), this is an attempt to mainline the fix for Micron's
> "shallow erase" issue. IMHO this is a "pretty way", not so invasive,
> with a limited performance penalty.
> 
> It has only be *compile-tested* and this is just to know if the
> approach is fine or not, then I will optimize, maybe rewrite a bit and
> forcibly (ask to) test it.
> 
> Happy new year!
> Miquèl
> 
> 
> Miquel Raynal (3):
>   mtd: rawnand: Add the nand_chip->erase hook
>   mtd: rawnand: Add the nand_chip->write_oob hook
>   mtd: rawnand: micron: Address the shallow erase issue
> 
>  data_buf                           | 29099 +++++++++++++++++++++++++++
>  databuf                            | 29099 +++++++++++++++++++++++++++

Those two files above should probably not be part of the patch submission.
-- 
Florian

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  parent reply	other threads:[~2020-01-02 18:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-31 19:26 [RFC PATCH 0/3] Fix proposal for the Micron shallow erase issue Miquel Raynal
2019-12-31 19:26 ` [RFC PATCH 1/3] mtd: rawnand: Add the nand_chip->erase hook Miquel Raynal
2019-12-31 19:26 ` [RFC PATCH 2/3] mtd: rawnand: Add the nand_chip->write_oob hook Miquel Raynal
2019-12-31 19:26 ` [RFC PATCH 3/3] mtd: rawnand: micron: Address the shallow erase issue Miquel Raynal
2020-01-02 18:41 ` Florian Fainelli [this message]
2020-01-14  9:12   ` [RFC PATCH 0/3] Fix proposal for the Micron " Miquel Raynal
2020-01-14 20:46     ` Wojtaszczyk, Piotr
2020-01-15  7:58       ` Boris Brezillon
2020-01-15  8:13         ` Miquel Raynal
2020-01-15 16:51           ` Wojtaszczyk, Piotr
2020-05-03 11:29             ` Miquel Raynal
2020-05-04  8:08               ` [EXT] " Bean Huo (beanhuo)
2020-05-04  8:26                 ` Miquel Raynal
2020-05-06 15:36                   ` Bean Huo (beanhuo)

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=a2199251-882a-5067-fe4c-47f1c8a252fe@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=Tudor.Ambarus@microchip.com \
    --cc=WojtaszczykP@cumminsallison.com \
    --cc=beanhuo@micron.com \
    --cc=boris.brezillon@collabora.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=tglx@linutronix.de \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vigneshr@ti.com \
    --cc=zszubbocsev@micron.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).