From: Brandon Philips <brandon@ifup.org>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>, shemminger@linux-foundation.org
Subject: [PATCH] TCP YeAH selects TCP Vegas with Kconfig
Date: Thu, 17 May 2007 11:54:29 -0700 [thread overview]
Message-ID: <20070517185429.GA882@ifup.org> (raw)
I tried building TCP YeAH into my kernel with TCP Vegas as a module and
the build failed because TCP YeAH depends on Vegas. This patch makes
Kconfig aware of the YeAH dependency on Vegas.
---
net/ipv4/Kconfig | 1 +
1 file changed, 1 insertion(+)
Index: linux-2.6/net/ipv4/Kconfig
===================================================================
--- linux-2.6.orig/net/ipv4/Kconfig
+++ linux-2.6/net/ipv4/Kconfig
@@ -577,6 +577,7 @@ config TCP_CONG_VENO
config TCP_CONG_YEAH
tristate "YeAH TCP"
depends on EXPERIMENTAL
+ select TCP_CONG_VEGAS
default n
---help---
YeAH-TCP is a sender-side high-speed enabled TCP congestion control
next reply other threads:[~2007-05-17 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 18:54 Brandon Philips [this message]
2007-05-17 20:42 ` [PATCH] TCP YeAH selects TCP Vegas with Kconfig David Miller
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=20070517185429.GA882@ifup.org \
--to=brandon@ifup.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).