On Mon, Jun 02, 2003 at 09:53:04AM +0200, Margit Schubert-While wrote:
> CONFIG_IPV6_SCTP__ is always being set to "y" even though
> not selected (CONFIG_IPV6 not set)
First, this doesn't do any harm since CONFIG_IPV6_SCTP__ alone doensn't
result in anything getting compiled.
But besides, it seems a bit broken.
<-- snip -->
default y if IPV6=n
default IPV6 if IPV6
tristate "The SCTP Protocol (EXPERIMENTAL)"
depends on IPV6_SCTP__
<-- snip -->
Semantically equivalent is the following for IPV6_SCTP__:
default y if IPV6=n || IPV6=y
default m if IPV6=m
If it was intended to disallow a static IP_SCTP with a modular IPV6 it
doesn't work: It's perfectly allowed to set IPV6=n and IP_SCTP=y and
later compile and install a modular IPV6 for the same kernel.
Could someone from the SCTP developers comment on the intentions behind
"Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jun 07 2003 - 22:00:19 EST