From: Adrian Bunk <bunk@fs.tum.de>
To: Margit Schubert-While <margitsw@t-online.de>,
lksctp-developers@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: SCTP config 2.5.70(-bk)
Date: Tue, 3 Jun 2003 15:03:08 +0200 [thread overview]
Message-ID: <20030603130308.GC27168@fs.tum.de> (raw)
In-Reply-To: <5.1.0.14.2.20030602094232.00aeda18@pop.t-online.de>
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.
>From net/sctp/Kconfig:
<-- snip -->
...
config IPV6_SCTP__
tristate
default y if IPV6=n
default IPV6 if IPV6
config IP_SCTP
tristate "The SCTP Protocol (EXPERIMENTAL)"
depends on IPV6_SCTP__
...
<-- snip -->
Semantically equivalent is the following for IPV6_SCTP__:
config IPV6_SCTP__
tristate
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
IPV6_SCTP__ ?
> Margit
cu
Adrian
--
"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
next prev parent reply other threads:[~2003-06-03 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 7:53 SCTP config 2.5.70(-bk) Margit Schubert-While
2003-06-03 13:03 ` Adrian Bunk [this message]
2003-06-03 21:07 ` [Lksctp-developers] " Jon Grimm
2003-06-07 19:12 ` Adrian Bunk
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=20030603130308.GC27168@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=margitsw@t-online.de \
--cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.