From: "Robert P. J. Day" <rpjday@mindspring.com>
To: netdev@vger.kernel.org
Cc: romieu@fr.zoreil.com
Subject: dscc4.c tests for "#ifndef MODULE" even though it must be modular
Date: Wed, 12 Sep 2007 09:25:04 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0709120918520.21350@localhost.localdomain> (raw)
from drivers/net/wan/dscc4.c:
=====
#ifndef MODULE
static int __init dscc4_setup(char *str)
{
int *args[] = { &debug, &quartz, NULL }, **p = args;
while (*p && (get_option(&str, *p) == 2))
p++;
return 1;
}
__setup("dscc4.setup=", dscc4_setup);
#endif
=====
but from drivers/net/wan/Kconfig:
...
config DSCC4
tristate "Etinc PCISYNC serial board support"
depends on HDLC && PCI && m
...
if i read this correctly, doesn't the depends on of "&& m" mean that
that Kconfig selection can be *at most* modular, so that that
preprocessor conditional can never be satisfied? a quick test under
"make menuconfig" seems to confirm that.
besides, the kernel parm being defined in that call to __setup()
really violates the spirit of defining kernel parms. :-)
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
reply other threads:[~2007-09-12 13:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.64.0709120918520.21350@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox