From: Mark Lord <lkml@rtr.ca>
To: Adrian Bunk <bunk@stusta.de>
Cc: jgarzik@pobox.com, tulip-users@lists.sourceforge.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] remove drivers/net/tulip/xircom_tulip_cb.c
Date: Fri, 18 Nov 2005 17:34:18 -0500 [thread overview]
Message-ID: <437E56EA.8070103@rtr.ca> (raw)
In-Reply-To: <20051118033306.GP11494@stusta.de>
Adrian Bunk wrote:
> This patch removes the obsolete drivers/net/tulip/xircom_tulip_cb.c
> driver.
>
> Is there any reason why it should be kept?
Yes. It is the only driver that works
without lockups on Xircom Cardbus cards.
Or so has been the case any time I've tried
the alternatives.
Is there any good reason to nuke it?
next prev parent reply other threads:[~2005-11-18 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 3:33 [RFC: 2.6 patch] remove drivers/net/tulip/xircom_tulip_cb.c Adrian Bunk
2005-11-18 22:34 ` Mark Lord [this message]
2005-11-19 20:43 ` Adrian Bunk
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=437E56EA.8070103@rtr.ca \
--to=lkml@rtr.ca \
--cc=bunk@stusta.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tulip-users@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;
as well as URLs for NNTP newsgroup(s).