From: Jeff Garzik <jgarzik@pobox.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Christoph Hellwig <hch@lst.de>,
netdev@oss.sgi.com, Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Pete Popov <ppopov@mvista.com>
Subject: Re: [PATCH] remove comx drivers from tree
Date: Sun, 16 May 2004 17:54:35 -0400 [thread overview]
Message-ID: <40A7E31B.5020705@pobox.com> (raw)
In-Reply-To: <m3sme1cqqg.fsf@defiant.pm.waw.pl>
Krzysztof Halasa wrote:
> While obviously I don't object (we should list removed things along
> with kernel version somewhere, though)... I could possibly port
> the drivers to my generic HDLC code, if someone sends me the hardware
> in question. Sure, I will never send it back, and it has to have V.35
> or V.24 interface, so I can connect it to something.
Then, *bang*, it's gone :)
We can resurrect if someone appears with hardware, and cares enough to
bring the driver back to life... Older kernels are archived on the
Internet forever, after all :)
Jeff
prev parent reply other threads:[~2004-05-16 21:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 11:17 [PATCH] remove comx drivers from tree Christoph Hellwig
2004-05-14 17:32 ` Jeff Garzik
2004-05-15 21:41 ` Krzysztof Halasa
2004-05-16 21:54 ` Jeff Garzik [this message]
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=40A7E31B.5020705@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=ppopov@mvista.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.