From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org,
pcmcia-cs-devel@lists.sourceforge.net,
linux-usb-devel@lists.sourceforge.net,
linux1394-devel@lists.sourceforge.net,
linux-scsi@vger.kernel.org
Subject: [ANNOUNCE] Linux Hotplug Developers Mailing List Created
Date: Sun, 7 Jan 2001 10:39:05 -0800 [thread overview]
Message-ID: <20010107103905.A11253@kroah.com> (raw)
Hi all,
With the release of the 2.4.0 kernel, there was a bit of confusion over
a last minute patch that made it in, which effected the modutils program
and the USB drivers hotplug ability. Realizing that this problem
shouldn't have happened with better communication between developers of
different parts of the kernel, and the fact that Linux hotplug
properties effect many different parts of the kernel, we have created a
new mailing list.
This list is for any developers interested in any aspects of the Linux
kernel hotplug ability and functionality. This would include (but is
not restricted to) USB, PCMCIA, SCSI, Firewire, and probably PCI
developers.
Information on joining the list can be found at:
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
There is an initial SourceForge site set up at:
http://sourceforge.net/projects/linux-hotplug/
but it is only currently holding the mailing list. In the future this
will hold more content. If anyone wants to be listed as a developer on
this project, please let me know.
If anyone knows of any other mailing lists this should be announced on,
please feel free to forward it.
thanks,
greg k-h
--
greg@(kroah|wirex).com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2001-01-07 18:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010107103905.A11253@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=pcmcia-cs-devel@lists.sourceforge.net \
/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