From: Kay Sievers <kay.sievers@vrfy.org>
To: David Brownell <david-b@pacbell.net>, dwmw2@infradead.org
Cc: Linux MTD <linux-mtd@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch/rfc 2.6.29 1/2] MTD: driver model updates
Date: Wed, 1 Apr 2009 01:51:48 +0200 [thread overview]
Message-ID: <ac3eb2510903311651i4c5f6805tc74fe04ee765be9c@mail.gmail.com> (raw)
In-Reply-To: <200903311418.53772.david-b@pacbell.net>
On Tue, Mar 31, 2009 at 23:18, David Brownell <david-b@pacbell.net> wrote:
> On Thursday 26 March 2009, David Brownell wrote:
>> From: David Brownell <dbrownell@users.sourceforge.net>
>>
>> Update driver model support in the MTD framework, so it fits
>> better into the current udev-based hotplug framework:
>
> Hmm, no comments? I had understood there was interest over on
> the MTD side of things in exposing more information through
> sysfs, to help avoid the need to add Even More Ioctls as part
> of support for things like NAND chips with 4KB pages, or which
> handle more than 4GBytes ...
Please have a look at this. We got asked repeatedly to provide better
hotplug/udev integration, and the patches, and having the parent
device properly assigned, would solve some of the problems people run
into currently.
Thanks,
Kay
next prev parent reply other threads:[~2009-03-31 23:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 7:42 David Brownell
2009-03-31 21:18 ` David Brownell
2009-03-31 23:51 ` Kay Sievers [this message]
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-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
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=ac3eb2510903311651i4c5f6805tc74fe04ee765be9c@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=david-b@pacbell.net \
--cc=dwmw2@infradead.org \
--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
all inboxes | Powered by JetHome®