linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: PATCH-remove experimental depends from forcedeth
Date: Sat, 05 Mar 2005 11:06:11 -0500	[thread overview]
Message-ID: <200503051106.11678.gene.heskett@verizon.net> (raw)

Greetings;

I've not seen a forcedeth mention go by on this list for quite some
time unless I made it.  It has been quite bulletproof here so I don't 
feel the need for it to remain dependent on the experimental status in 
the main .config.

Hence this patch to remove that requirement from the appropriate 
Kconfig.

Signed-off-by Gene Heskett <gene.heskett@verizon.net>

/usr/src/linux-2.6.11/drivers/net/Kconfig | 2+-
 one file changed, 2 deletions, 2 insertions

--- drivers/net/Kconfig.old 2005-03-05 10:43:45.000000000 -0500
+++ drivers/net/Kconfig 2005-03-05 11:01:01.000000000 -0500
@@ -1342,8 +1342,8 @@ config B44
    called b44.
 
 config FORCEDETH
- tristate "Reverse Engineered nForce Ethernet support (EXPERIMENTAL)"
- depends on NET_PCI && PCI && EXPERIMENTAL
+ tristate "Reverse Engineered nForce Ethernet support"
+ depends on NET_PCI && PCI
  help
    If you have a network (Ethernet) controller of this type, say Y and
    read the Ethernet-HOWTO, available from

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.34% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.

             reply	other threads:[~2005-03-05 16:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-05 16:06 Gene Heskett [this message]
2005-04-24 20:30 ` PATCH-remove experimental depends from forcedeth Daniel Drake

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=200503051106.11678.gene.heskett@verizon.net \
    --to=gene.heskett@verizon.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;
as well as URLs for NNTP newsgroup(s).