From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Matthieu CASTET <matthieu.castet@parrot.com>
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 18:03:32 +0100 [thread overview]
Message-ID: <20130221170332.GK32249@pengutronix.de> (raw)
In-Reply-To: <20130221100728.GI32249@pengutronix.de>
Hello,
On Thu, Feb 21, 2013 at 11:07:28AM +0100, Uwe Kleine-König wrote:
> > Shouldn't vendor specific code go in another file ?
> OK for me, I didn't notice any other vendor specific code and e.g. onfi
> stuff is in nand_base, too. (Maybe that is because it's not possible to
> see from the filenames under drivers/mtd/nand if that file defines a
> controller driver or some chip specific stuff.)
>
> I will move it to a file nandchip-micron.c for the next submission. Does
> this look right? I will wait for more feedback though.
I started to implement that now and one problem is that a few functions
(namely nand_get_device, nand_release_device and nand_onfi_set_features)
are statically defined in nand_base.c. The obvious options are:
1) drop "static" from nand_get_device et al. and declare them in a
header (say drivers/mtd/nand/nand.h);
2) keep the implementation of the Micron stuff in nand_base.c; or
3) put it into a nandchip-micron.c and #include that from nand_base.c
Did I miss something? David, Artem: Any thoughts/preferences?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2013-02-21 17:03 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
2013-02-21 10:07 ` Uwe Kleine-König
2013-02-21 17:03 ` Uwe Kleine-König [this message]
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=20130221170332.GK32249@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=artem.bityutskiy@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=kernel@pengutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=matthieu.castet@parrot.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