From: Chris Snook <csnook@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: atl1-devel@lists.sourceforge.net,
Jay Cliburn <jacliburn@bellsouth.net>,
netdev@vger.kernel.org
Subject: [PATCH 1/2] atl1: add CONFIG_ATL1_EXPERIMENTAL to kconfig
Date: Fri, 7 Sep 2007 19:47:46 -0400 [thread overview]
Message-ID: <20070907234746.GA12055@shell.boston.redhat.com> (raw)
In-Reply-To: <46E1E1AC.5030801@redhat.com>
From: Chris Snook <csnook@redhat.com>
Introduce Kconfig ATL1_EXPERIMENTAL to separate mature code from less mature
code in the atl1 driver, and remove EXPERIMENTAL designation for ATL1.
Signed-off-by: Chris Snook <csnook@redhat.com>
Acked-by: Jay Cliburn <jacliburn@bellsouth.net>
--- a/drivers/net/Kconfig 2007-09-04 10:12:38.000000000 -0400
+++ b/drivers/net/Kconfig 2007-09-04 10:37:34.000000000 -0400
@@ -2329,8 +2329,8 @@ config QLA3XXX
will be called qla3xxx.
config ATL1
- tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)"
- depends on PCI && EXPERIMENTAL
+ tristate "Attansic L1 Gigabit Ethernet support"
+ depends on PCI
select CRC32
select MII
help
@@ -2339,6 +2339,16 @@ config ATL1
To compile this driver as a module, choose M here. The module
will be called atl1.
+config ATL1_EXPERIMENTAL
+ bool "atl1 experimental features"
+ depends on ATL1 && EXPERIMENTAL
+ help
+ This option enables various features that have not yet reached
+ the maturity of the rest of the atl1 driver. The driver will
+ still work fine without this option enabled.
+
+ If unsure, say N.
+
endif # NETDEV_1000
#
next prev parent reply other threads:[~2007-09-07 23:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 23:41 [PATCH 0/2] atl1: Introduce CONFIG_ATL1_EXPERIMENTAL Chris Snook
2007-09-07 23:47 ` Chris Snook [this message]
2007-09-07 23:52 ` [PATCH 2/2] atl1: wrap problematic optimizations in CONFIG_ATL1_EXPERIMENTAL Chris Snook
2007-09-08 0:21 ` [atl1-devel] " Luca
2007-09-08 0:27 ` Chris Snook
2007-09-07 23:54 ` [PATCH 0/2] atl1: Introduce CONFIG_ATL1_EXPERIMENTAL Jeff Garzik
2007-09-08 0:06 ` Chris Snook
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=20070907234746.GA12055@shell.boston.redhat.com \
--to=csnook@redhat.com \
--cc=atl1-devel@lists.sourceforge.net \
--cc=jacliburn@bellsouth.net \
--cc=jeff@garzik.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).