From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: Boris Brezillon <boris.brezillon@bootlin.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Richard Weinberger <richard@nod.at>,
"Marek Vasut" <marek.vasut@gmail.com>
Subject: Re: [RFC PATCH v2 5/6] mtd: rawnand: micron: add ONFI_FEATURE_ON_DIE_ECC to supported features
Date: Wed, 20 Jun 2018 09:43:42 +0200 [thread overview]
Message-ID: <20180620094342.6689f0d4@xps13> (raw)
In-Reply-To: <b7bfe97c079e4e83bc108625224c2b16@svr-chch-ex1.atlnz.lc>
Hi Chris,
On Tue, 19 Jun 2018 21:22:00 +0000, Chris Packham
<Chris.Packham@alliedtelesis.co.nz> wrote:
> On 19/06/18 18:53, Miquel Raynal wrote:
> > Hi Boris, Chris,
> >
> > On Tue, 19 Jun 2018 07:40:56 +0200, Boris Brezillon
> > <boris.brezillon@bootlin.com> wrote:
> >
> >> On Tue, 19 Jun 2018 17:31:24 +1200
> >> Chris Packham <chris.packham@alliedtelesis.co.nz> wrote:
> >>
> >>> Add ONFI_FEATURE_ON_DIE_ECC to the set/get features list for Micron
> >>> NAND flash.
> >>>
> >>
> >> Fixes: 789157e41a06 ("mtd: rawnand: allow vendors to declare (un)supported features")
> >
> > Sorry for breaking it in my previous series.
> >
> >> Cc: <stable@vger.kernel.org>
> >>
> >> No need to send a new version, I'll add that when queuing the patch.
> >>
> >> Miquel, if you're okay, I'm gonna take this patch in the mtd/fixes branch
> >> and let you deal with other patches in this series.
> >
> > Yes please, take this one.
> >
> > * Chris, I'll take patches 1, 2, 3 with Boris comments.
>
> OK.
>
> I also got a kbuild report on
>
> include/linux/mtd/rawnand.h:788: warning: Function parameter or member
> 'fixup_onfi_param_page' not described in 'nand_manufacturer_ops'
>
> Do you want me to send a v3 for that? (given our timezones I'll just
> send it anyway and you can choose to take it or just stick with v2).
I'll take v3 for sure, thanks for already sending it.
>
> > * Patch 4 I think I'll just drop it as nobody can test it (and it's a
> > oneliner). I prefer people requesting a feature than complaining
> > about a bug :)
>
> Agreed. It's in the mailing list archive now if someone needs it we can
> resurrect it from there
>
> > * Boris will take patch 5 in the mtd/fixes branch.
>
> Thanks all. Sorry our emails crossed so I couldn't just send #5 as a fix
> on it's own.
>
> > * I'll let you write a v3 for patch 6 only.
>
> I'll have a read through the old thread and see if I can make sense of it.
Thanks!
Miquèl
next prev parent reply other threads:[~2018-06-20 7:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 5:31 [RFC PATCH v2 0/6] mtd: rawnand: support MT29F1G08ABAFAWP-ITE:F Chris Packham
2018-06-19 5:31 ` [RFC PATCH v2 1/6] mtd: rawnand: marvell: Handle on-die ECC Chris Packham
2018-06-19 5:58 ` Boris Brezillon
2018-06-19 5:31 ` [RFC PATCH v2 2/6] mtd: rawnand: add manufacturer fixup for ONFI parameter page Chris Packham
2018-06-19 6:01 ` Boris Brezillon
2018-06-19 5:31 ` [RFC PATCH v2 3/6] mtd: rawnand: micron: add fixup for ONFI revision Chris Packham
2018-06-19 6:02 ` Boris Brezillon
2018-06-19 5:31 ` [RFC PATCH v2 4/6] mtd: rawnand: marvell: Support page size of 2048 with 8-bit ECC Chris Packham
2018-06-19 5:31 ` [RFC PATCH v2 5/6] mtd: rawnand: micron: add ONFI_FEATURE_ON_DIE_ECC to supported features Chris Packham
2018-06-19 5:40 ` Boris Brezillon
2018-06-19 6:52 ` Miquel Raynal
2018-06-19 21:22 ` Chris Packham
2018-06-20 7:43 ` Miquel Raynal [this message]
2018-06-19 9:00 ` Miquel Raynal
2018-06-20 9:40 ` Boris Brezillon
2018-06-19 5:31 ` [RFC PATCH v2 6/6] mtd: rawnand: micron: support 8/512 on-die ECC Chris Packham
2018-06-19 6:09 ` 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=20180620094342.6689f0d4@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).