From: Matthieu CASTET <matthieu.castet@parrot.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
David Woodhouse <dwmw2@infradead.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH RFC] mtd/nand: implement user otp for Micron chips
Date: Thu, 21 Feb 2013 10:47:28 +0100 [thread overview]
Message-ID: <5125ED30.3020305@parrot.com> (raw)
In-Reply-To: <1361394332-19415-1-git-send-email-u.kleine-koenig@pengutronix.de>
Uwe Kleine-König a écrit :
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> Hello,
>
> there are some things to clean up before this patch can be applied. See
> the respective comments in the code, most of them are marked with XXX,
> but I'm sure you'll find things to criticize that I didn't mark :-)
>
> About the unsuitablity of nand_do_read_ops and nand_do_write_ops I'd like to
> hear your thoughts. Would you prefer a new function that does only the
> necessary stuff, or should I add another parameter to make them do the
> right thing for me?
>
> BTW, to make use of this patch you'd need
> http://patchwork.ozlabs.org/patch/221191/
>
> Best regards
> Uwe
>
> drivers/mtd/nand/nand_base.c | 126 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 126 insertions(+)
>
> diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c
> index 3766682..10e51f3 100644
> --- a/drivers/mtd/nand/nand_base.c
> +++ b/drivers/mtd/nand/nand_base.c
> @@ -2753,6 +2753,116 @@ static int nand_onfi_get_features(struct mtd_info *mtd, struct nand_chip *chip,
> return 0;
Shouldn't vendor specific code go in another file ?
Matthieu
next prev parent reply other threads:[~2013-02-21 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 21:05 [PATCH RFC] mtd/nand: implement user otp for Micron chips Uwe Kleine-König
2013-02-21 9:47 ` Matthieu CASTET [this message]
2013-02-21 10:07 ` Uwe Kleine-König
2013-02-21 17:03 ` Uwe Kleine-König
2013-03-04 17:00 ` [PATCH] " Uwe Kleine-König
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=5125ED30.3020305@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=kernel@pengutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.