From: Andrea Barisani <lcars@infis.univ.trieste.it>
To: linux-kernel@vger.kernel.org
Subject: kernel 2.6.0, wrong Kconfig directives
Date: Tue, 23 Dec 2003 00:56:23 +0100 [thread overview]
Message-ID: <20031222235622.GA17030@sole.infis.univ.trieste.it> (raw)
Hi folks,
Installing 2.6.0 I've found that some kernel options directives are wrong,
in fact the option turns out to be always enabled. I don't think this is
a desired behaviour.
Sorry for the format, yes I know it's ugly :) but I'll leave to you the proper
solution :) so I can't make a proper patch.
- IPV6_SCTP___ option is always turned on
./net/sctp/Kconfig:
8: config IPV6_SCTP__
9: tristate
10: default y if IPV6=n
11: default IPV6 if IPV6
12:
13: config IP_SCTP
14: tristate "The SCTP Protocol (EXPERIMENTAL)"
15: depends on IPV6_SCTP__
I think something is wrong here, why the 'default y if IPV6=n' ???
- INPUT_MOUSEDEV option is always turned on
./drivers/input/Kconfig:
27: config INPUT_MOUSEDEV
28: tristate "Mouse interface" if EMBEDDED
29: default y
30: depends on INPUT
43: config INPUT_MOUSEDEV_PSAUX
44: bool "Provide legacy /dev/psaux device" if EMBEDDED
45: default y
46: depends on INPUT_MOUSEDEV
the tristate directive is ignored in most default configurations since EMBEDDED
is not set, however this doesn't allow to disable INPUT_MOUSEDEV and
INPUT_MOUSEDEV_PSAUX. I don't suppose this is right.
- SOUND_GAMEPORT option is always turned on
./drivers/input/gameport/Kconfig
22: config SOUND_GAMEPORT
23: tristate
24: default y if GAMEPORT!=m
25: default m if GAMEPORT=m
line 24 is definetly wrong, option is enabled if GAMEPORT=n.
Bye
P.S.
I'm not subscribed to this list so CC me if it's needed
--
------------------------------------------------------------
INFIS Network Administrator & Security Officer .*.
Department of Physics - University of Trieste V
lcars@infis.univ.trieste.it - GPG Key 0x864C9B9E ( )
---------------------------------------------------- ( )
"How would you know I'm mad?" said Alice. ^^-^^
"You must be,'said the Cat,'or you wouldn't have come here."
------------------------------------------------------------
next reply other threads:[~2003-12-22 23:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 23:56 Andrea Barisani [this message]
2003-12-25 19:20 ` OGAWA Hirofumi
2003-12-25 19:51 ` Muli Ben-Yehuda
2003-12-25 20:33 ` OGAWA Hirofumi
2003-12-25 20:38 ` Muli Ben-Yehuda
2003-12-25 21:25 ` OGAWA Hirofumi
2003-12-26 1:23 ` OGAWA Hirofumi
2003-12-25 19:39 ` Muli Ben-Yehuda
2004-01-05 22:17 ` Adrian Bunk
2004-01-05 22:59 ` Andrea Barisani
2004-01-06 1:22 ` 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=20031222235622.GA17030@sole.infis.univ.trieste.it \
--to=lcars@infis.univ.trieste.it \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®