Skip to contentSkip to conversation

let TCP_CONG_ADVANCED default to n

PATCH In review Adrian Bunk 2 participants 2 messages Jun 26, 2005 Networking

lore
Share & tools
lore

Adrian Bunk

author
#0 lore raw

PATCH 1/1 let TCP_CONG_ADVANCED default to n

It doesn't seem to make much sense to let an "If unsure, say N." option default to y.

Signed-off-by Adrian Bunk <[email protected]>
net/ipv4/Kconfig renamed from net/ipv4/Kconfig.old +0 -1
@@ -442,19 +442,18 @@
 	  
 	  If unsure, say Y.
 
 config IP_TCPDIAG_IPV6
 	def_bool (IP_TCPDIAG=y && IPV6=y) || (IP_TCPDIAG=m && IPV6)
 
 config TCP_CONG_ADVANCED
 	bool "TCP: advanced congestion control"
 	depends on INET
-	default y
 	---help---
 	  Support for selection of various TCP congestion control
 	  modules.
 
 	  Nearly all users can safely say no here, and a safe default
 	  selection will be made (BIC-TCP with new Reno as a fallback).
 
 	  If unsure, say N.