From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Gabriel C <nix.or.die@googlemail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH] IP_VS should depend on EXPERIMENTAL ?
Date: Fri, 20 Jul 2007 08:11:45 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707200805070.11571@localhost.localdomain> (raw)
In-Reply-To: <46A0A01A.7030403@googlemail.com>
as a short followup to my previous post, at the *very least*, a
cleanup that could be done now is to find all entries which have an
actual dependency on "EXPERIMENTAL" but don't advertise themselves as
such:
...
config MA600_DONGLE
tristate "Mobile Action MA600 dongle"
depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
...
and determine which of those should have the dependency on
"EXPERIMENTAL" removed. no, don't go adding "(EXPERIMENTAL)" to the
prompt -- just deal with *only* those for which the dependency is
clearly out of date and not relevant anymore, and delete it.
that would be, at least, a place to start. and, yes, there's piles of
potential (net/ipv4/Kconfig):
config TCP_CONG_HSTCP
tristate "High Speed TCP"
depends on EXPERIMENTAL
...
config TCP_CONG_HYBLA
tristate "TCP-Hybla congestion control algorithm"
depends on EXPERIMENTAL
...
config TCP_CONG_VEGAS
tristate "TCP Vegas"
depends on EXPERIMENTAL
...
... etc etc ...
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
prev parent reply other threads:[~2007-07-20 12:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 11:44 [PATCH] IP_VS should depend on EXPERIMENTAL ? Gabriel C
2007-07-20 11:59 ` Robert P. J. Day
2007-07-20 12:17 ` Gabriel C
2007-07-20 12:21 ` Robert P. J. Day
2007-07-20 12:32 ` Gabriel C
2007-07-20 13:04 ` Robert P. J. Day
2007-07-20 12:11 ` Robert P. J. Day [this message]
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=Pine.LNX.4.64.0707200805070.11571@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nix.or.die@googlemail.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