From: Richard Weinberger <richard@nod.at>
To: "Bean Huo (beanhuo)" <beanhuo@micron.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
"Zoltan Szubbocsev (zszubbocsev)" <zszubbocsev@micron.com>,
Boris Brezillon <bbrezillon@kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: [EXT] Re: [PATCH V1] mtd: core: Micron SLC NAND filling block
Date: Wed, 19 Dec 2018 19:31:17 +0100 [thread overview]
Message-ID: <3542497.Sqr1i8Hk3A@blindfold> (raw)
In-Reply-To: <BYAPR08MB45331E5653451102C61BAC54DBBE0@BYAPR08MB4533.namprd08.prod.outlook.com>
Bean,
Am Mittwoch, 19. Dezember 2018, 18:19:43 CET schrieb Bean Huo (beanhuo):
> Hi, Boris and Miquel
> Thanks for your email.
> Since the patch is based on v4.2 which doesn't separate specific NAND vendor
> driver into vendor specific chip driver file. I will rebase my patch to latest linux kernel,
> and implement a specific hook funciton in the nand_micron.c as you suggested.
> After testing well, you will see the version 2.
Please also check your patch using checkpatch.pl to make sure it matches the kernel coding style.
Can we also limit the workaround to a subset of Micron NANDs?
Enabling it for every kind of Micron NAND seems overkill to me.
Maybe you can precise "legacy planar 2D Micron NAND devices" bit more. :-)
Thanks,
//richard
next prev parent reply other threads:[~2018-12-19 18:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 11:03 [PATCH V1] mtd: core: Micron SLC NAND filling block Bean Huo (beanhuo)
2018-12-19 13:17 ` Boris Brezillon
2018-12-19 13:59 ` [EXT] " Zoltan Szubbocsev (zszubbocsev)
2018-12-19 14:17 ` Miquel Raynal
2018-12-19 17:19 ` Bean Huo (beanhuo)
2018-12-19 18:31 ` Richard Weinberger [this message]
2018-12-19 18:46 ` Boris Brezillon
2018-12-19 14:27 ` Richard Weinberger
2018-12-19 18:11 ` [EXT] " Bean Huo (beanhuo)
2018-12-19 18:28 ` Richard Weinberger
2018-12-19 18:44 ` Boris Brezillon
2018-12-19 22:29 ` Thomas Gleixner
2019-01-02 13:34 ` 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=3542497.Sqr1i8Hk3A@blindfold \
--to=richard@nod.at \
--cc=bbrezillon@kernel.org \
--cc=beanhuo@micron.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=tglx@linutronix.de \
--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