From: Lee Revell <rlrevell@joe-job.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: jgarzik@pobox.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] CONFIG_FORCEDETH updates
Date: Sun, 12 Feb 2006 17:03:36 -0500 [thread overview]
Message-ID: <1139781817.19342.300.camel@mindpipe> (raw)
In-Reply-To: <20060212175202.GK30922@stusta.de>
On Sun, 2006-02-12 at 18:52 +0100, Adrian Bunk wrote:
> This patch contains the following possible updates:
> - let FORCEDETH no longer depend on EXPERIMENTAL
> - remove the "Reverse Engineered" from the option text:
> for the user it's important which hardware the driver supports, not
> how it was developed
Is this driver as stable as one that was developed with proper
documentation? I prefer to know that something as elementary as a fast
ethernet controller had to be reverse engineered so I can avoid
supporting a vendor so hostile to Linux.
Lee
next prev parent reply other threads:[~2006-02-12 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 17:52 [RFC: 2.6 patch] CONFIG_FORCEDETH updates Adrian Bunk
2006-02-12 22:03 ` Lee Revell [this message]
2006-02-12 22:47 ` Alistair John Strachan
2006-02-13 8:36 ` Arthur Othieno
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=1139781817.19342.300.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=bunk@stusta.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).