LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Jeff Garzik <jgarzik@pobox.com>
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: Sat, 15 May 2004 23:41:59 +0200 [thread overview]
Message-ID: <m3sme1cqqg.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <40A50292.3070601@pobox.com> (Jeff Garzik's message of "Fri, 14 May 2004 13:32:02 -0400")
Jeff Garzik <jgarzik@pobox.com> writes:
> I have applied this to my netdev-2.6 tree, and so it should show up in
> -mm sometime.
>
> drivers/net/wan/Kconfig | 113 -
> drivers/net/wan/Makefile | 8
> drivers/net/wan/comx-hw-comx.c | 1449 -------------------
> drivers/net/wan/comx-hw-locomx.c | 495 ------
> drivers/net/wan/comx-hw-mixcom.c | 959 ------------
> drivers/net/wan/comx-hw-munich.c | 2853
> --------------------------------------
> drivers/net/wan/comx-proto-fr.c | 1013 -------------
> drivers/net/wan/comx-proto-lapb.c | 550 -------
> drivers/net/wan/comx-proto-ppp.c | 268 ---
> drivers/net/wan/comx.c | 1127 ---------------
> drivers/net/wan/comx.h | 231 ---
> drivers/net/wan/comxhw.h | 112 -
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.
--
Krzysztof Halasa, B*FH
next prev parent reply other threads:[~2004-05-15 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040507111725.GA11575@lst.de>
2004-05-14 17:32 ` [PATCH] remove comx drivers from tree Jeff Garzik
2004-05-15 21:41 ` Krzysztof Halasa [this message]
2004-05-16 21:54 ` Jeff Garzik
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=m3sme1cqqg.fsf@defiant.pm.waw.pl \
--to=khc@pm.waw.pl \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=jgarzik@pobox.com \
--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 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).