From: Todd Poynor <tpoynor@mvista.com>
To: Greg KH <greg@kroah.com>
Cc: linux-hotplug-devel@lists.sourceforge.net,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Hotplug for device power state changes
Date: Mon, 03 May 2004 21:33:02 +0000 [thread overview]
Message-ID: <4096BA8E.4040601@mvista.com> (raw)
In-Reply-To: <20040501014827.GA16006@kroah.com>
Greg KH wrote:
> I don't have an objection to add such a new paramater (or even a new
> function call like you suggested), just don't go messing with the main
> kobject hotplug call without thinking everything through :)
OK, will do.
>>This is something that was requested of me by others who build Linux
>>into consumer electronics devices. Perhaps some of the interested
>>parties may speak up here to add more insight.
>
>
> Please encourage them to speak up. I hear _nothing_ from any embedded
> developers, and I am really interested in how the driver model and
> hotplug works (or doesn't) for them. Without that feedback, we are in
> the dark as to what their needs/hates are.
Thanks, I have passed the call to get involved on to a group of Linux
consumer electronics developers (the Consumer Electronics Linux Forum;
Tim Bird will hold a BoF at OLS introducing this group). I am involved
at an infrastructure level and have helped steer various general
requirements toward use of LDM (which we've been using even in 2.4 for
some time) and hotplug (which is new to us for these purposes and they
might not yet have much experience with this), and can also serve as a
conduit for feedback. I appreciate your interest in the needs of
embedded developers and hope that we can contribute some useful
suggestions and features.
--
Todd Poynor
MontaVista Software
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_idÅ66&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-05-03 21:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040429202654.GA9971@dhcp193.mvista.com>
2004-04-29 21:42 ` [PATCH] Hotplug for device power state changes Russell King
2004-04-29 22:36 ` Todd Poynor
2004-04-30 0:50 ` Benjamin Herrenschmidt
2004-04-30 8:30 ` Russell King
2004-04-30 19:59 ` Todd Poynor
2004-04-30 21:56 ` Greg KH
2004-05-01 1:16 ` Todd Poynor
2004-05-01 1:48 ` Greg KH
2004-05-03 21:33 ` Todd Poynor [this message]
2004-05-01 0:03 ` Nigel Cunningham
2004-05-03 22:04 ` Todd Poynor
2004-04-30 19:07 ` Todd Poynor
2004-05-15 1:40 ` Nicolas Pitre
2004-05-15 23:34 ` Pavel Machek
[not found] ` <Pine.LNX.4.50.0405040819490.3562-100000@monsoon.he.net>
2004-05-04 20:36 ` Todd Poynor
[not found] ` <Pine.LNX.4.50.0405042110440.30304-100000@monsoon.he.net>
2004-05-06 1:08 ` Todd Poynor
2004-05-14 2:50 ` Pavel Machek
2004-05-15 2:08 ` Todd Poynor
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=4096BA8E.4040601@mvista.com \
--to=tpoynor@mvista.com \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).