From: Miles Lane <miles@megapathdsl.net>
To: Jeff Garzik <jgarzik@mandrakesoft.mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org, linux-hotplug-devel@lists.sourceforge.net
Subject: Re: Adding PCMCIA support to the kernel tree -- developers needed.
Date: Sat, 03 Feb 2001 16:00:46 -0800 [thread overview]
Message-ID: <3A7C9BAE.45DB2F09@megapathdsl.net> (raw)
In-Reply-To: <Pine.LNX.3.96.1010203040618.29269C-100000@mandrakesoft.mandrakesoft.com>
Jeff Garzik wrote:
>
> On Fri, 2 Feb 2001, Miles Lane wrote:
> > I asked David Hinds to write up an outline of the things that
> > will be needed to get PCMCIA support cleanly and completely
> > integrated into the kernel tree.
> >
> > David has expressed that he'll not be able to participate in
> > this work. He has his hands full with his day job and his
> > role as maintainer/developer of the pcmcia-cs package.
> [...]
> > Anyone willing to sign up for some of this effort?
>
> I'll convert all the network drivers once a design is agreed upon.
Would you write up a proposal for this design that we could work
from to come to a agreed design? You are probably the best person
to start this process.
Thanks!
Miles
-
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/
next prev parent reply other threads:[~2001-02-03 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A711BB1.C5B8BCFB@megapathdsl.net>
[not found] ` <3A711CB1.62757B52@megapathdsl.net>
[not found] ` <20010131200621.F29731@sonic.net>
[not found] ` <3A78E3EC.8050605@megapathdsl.net>
[not found] ` <20010202183642.F30100@sonic.net>
2001-02-03 7:28 ` Adding PCMCIA support to the kernel tree -- developers needed Miles Lane
2001-02-03 10:07 ` Jeff Garzik
2001-02-04 0:00 ` Miles Lane [this message]
2001-02-05 1:14 ` Jeff Garzik
2001-02-05 2:43 ` Miles Lane
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=3A7C9BAE.45DB2F09@megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=jgarzik@mandrakesoft.mandrakesoft.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