From: David Woodhouse <dwmw2@infradead.org>
To: Kevin Cernekee <kpc.mtd@gmail.com>
Cc: David Brownell <david-b@pacbell.net>,
Linux MTD <linux-mtd@lists.infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch/rfc 2.6.29 1/2] MTD: driver model updates
Date: Sat, 04 Apr 2009 15:36:37 +0100 [thread overview]
Message-ID: <1238855797.4068.6.camel@macbook.infradead.org> (raw)
In-Reply-To: <a95a62fe0904031300i82bdf42h5bc854a002e0091e@mail.gmail.com>
On Fri, 2009-04-03 at 13:00 -0700, Kevin Cernekee wrote:
> Based on: http://lists.infradead.org/pipermail/linux-mtd/2009-March/025005.html
>
> My only change from the previous posting
> (http://lists.infradead.org/pipermail/linux-mtd/2009-April/025121.html)
> was to remove the "mtd_" prefix on the device attributes.
>
> David's 2/2 patch
> (http://lists.infradead.org/pipermail/linux-mtd/2009-March/025011.html)
> may still be used as-is.
>
> Signed-off-by: Kevin Cernekee <kpc.mtd@gmail.com>
Thanks, this looks like a very good start in the direction we need to
go. I've applied David's patches as well as the changes from this one,
and hooked it up for the CAFÉ NAND controller too.
Since the callers are passing a struct mtd_info * into nand_scan(), it
doesn't seem necessary to pass the device in too; they can just set it
for themselves. Passing it in to the NOR chip probe routines might make
sense though.
I'm not worried about a flag day for _internal_ stuff -- for 2.6.31 I
think I'm going to add a WARN_ON(&mtd->dev.parent) into the core code.
I really do think I want this to avoid the need for 64-bit ioctls
(except maybe MEMERASE64).
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2009-04-04 14:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 7:42 [patch/rfc 2.6.29 1/2] MTD: driver model updates David Brownell
2009-03-31 21:18 ` David Brownell
2009-03-31 23:51 ` Kay Sievers
2009-04-01 13:43 ` Juergen Beisert
2009-04-01 1:17 ` Kevin Cernekee
2009-04-01 3:21 ` David Brownell
2009-04-01 4:49 ` Kevin Cernekee
2009-04-01 6:36 ` David Brownell
2009-04-01 7:29 ` Ricard Wanderlof
2009-04-01 7:51 ` Artem Bityutskiy
2009-04-01 8:05 ` David Brownell
2009-04-01 8:25 ` Ricard Wanderlof
2009-04-01 8:28 ` Artem Bityutskiy
2009-04-02 23:41 ` Kevin Cernekee
2009-04-03 7:03 ` Artem Bityutskiy
2009-04-03 7:09 ` Artem Bityutskiy
2009-04-03 20:00 ` Kevin Cernekee
2009-04-04 14:36 ` David Woodhouse [this message]
2009-04-04 16:17 ` Kevin Cernekee
2009-04-04 16:20 ` David Brownell
2009-04-04 16:29 ` David Woodhouse
2009-04-04 17:18 ` David Brownell
2009-04-06 5:34 ` Greg KH
2009-04-03 10:04 ` David Woodhouse
2009-04-03 17:24 ` David Brownell
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=1238855797.4068.6.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=david-b@pacbell.net \
--cc=kpc.mtd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
/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