From: Joel Schopp <jschopp@austin.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Lhms-devel] Hotplug SIG
Date: Thu, 12 Aug 2004 20:14:49 +0000 [thread overview]
Message-ID: <411BCFB9.5000902@austin.ibm.com> (raw)
In-Reply-To: <1092325835.3204.15.camel@nighthawk>
<snip>
> As the SIG leader I will make it a point to keep
> you inform through the existing mailing lists of our progress and come
> to you with questions/comments/discussions.
Please do not cross post in the future. While doing so one time is
probably OK it is not a good habit to get into. Try to carry out
discussion on the actual sig mailing list you set up, which you forgot
to refer people to. This will be my only email on this subject not
directed at that list, and this one only because I don't think others
are aware of its existence yet.
http://lists.osdl.org/mailman/listinfo/hotplug_sig
> For those of you unfamiliar with the concept of OSDL SIGs, they are
> temporary groups created to work on specific areas i.e we'll figure out
> what needs to be done, write code for it, get it submitted and accepted,
> provide documentation when required and disband.
I, and I would guess several others, are skeptical that you are not
trying to preempt and/or control the work already being done by the
community. I'm giving you the benefit of the doubt for now. I hope
others will do the same.
>
> After this lengthy introduction here is my request to you:
> If there are any tasks or features that you would like to get done but
> don't have the time or resource to do them yourself or within your group
> please let us know. Again right now the SIG is reaching out to everyone
> but as we get more educated we will only focus on what needs to be done.
> Also remember that a lot of OSDL members are vendors and as such have
> access to prototype hardware for testing.
I've worked on cpu hotplug, am now working on memory hotplug, and am
somewhat involved in pci hotplug.
What I see as common unfulfilled needs are:
1. Documentation and more documentation.
2. Constant regression testing. As not a lot of people have hardware
that supports various hotplug and they are not enabled by default new
features tend to break them.
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
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-08-12 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 15:50 [Lhms-devel] Hotplug SIG Dave Hansen
2004-08-12 19:02 ` Silbermann, Martine
2004-08-12 20:14 ` Joel Schopp [this message]
2004-08-13 14:54 ` Silbermann, Martine
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=411BCFB9.5000902@austin.ibm.com \
--to=jschopp@austin.ibm.com \
--cc=linux-hotplug@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).