From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.5-ac12: 3c590.c: Warning about 'nopnp' parameter
Date: Tue, 12 Jun 2001 02:02:14 +0200 [thread overview]
Message-ID: <20010611235220Z264082-17720+2933@vger.kernel.org> (raw)
In-Reply-To: <10820.992234920@ocs4.ocs-net>
In-Reply-To: <10820.992234920@ocs4.ocs-net>
Am Montag, 11. Juni 2001 06:48 schrieb Keith Owens:
> On Mon, 11 Jun 2001 04:35:42 +0200,
>
> Dieter =?iso-8859-1?q?N=FCtzel?= <Dieter.Nuetzel@hamburg.de> wrote:
> >insmod: Warning: /lib/modules/2.4.5-ac12/kernel/drivers/net/3c509.o symbol
> >for parameter nopnp not found
>
> MODULE_PARM(nopnp) is in open code but the declaration of nopnp is
> wrapped in #ifdef CONFIG_ISAPNP. The module parm needs to be wrapped
> in #ifdef CONFIG_ISAPNP as well. Against 2.4.5-ac13.
>
> Index: 5.35/drivers/net/3c509.c
> --- 5.35/drivers/net/3c509.c Sat, 09 Jun 2001 17:17:16 +1000 kaos
> (linux-2.4/l/c/31_3c509.c 1.2.1.6 644) +++ 5.35(w)/drivers/net/3c509.c Mon,
> 11 Jun 2001 14:47:01 +1000 kaos (linux-2.4/l/c/31_3c509.c 1.2.1.6 644) @@
> -1014,8 +1014,10 @@ MODULE_PARM_DESC(debug, "EtherLink III d
> MODULE_PARM_DESC(irq, "EtherLink III IRQ number(s) (assigned)");
> MODULE_PARM_DESC(xcvr,"EtherLink III tranceiver(s) (0=internal,
> 1=external)"); MODULE_PARM_DESC(max_interrupt_work, "EtherLink III maximum
> events handled per interrupt"); +#ifdef CONFIG_ISAPNP
> MODULE_PARM(nopnp, "i");
> MODULE_PARM_DESC(nopnp, "EtherLink III disable ISA PnP support (0-1)");
> +#endif /* CONFIG_ISAPNP */
>
> int
> init_module(void)
It calmed it.
Thanks,
Dieter
prev parent reply other threads:[~2001-06-11 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 2:35 Dieter Nützel
2001-06-11 4:48 ` Keith Owens
2001-06-12 0:02 ` Dieter Nützel [this message]
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=20010611235220Z264082-17720+2933@vger.kernel.org \
--to=dieter.nuetzel@hamburg.de \
--cc=kaos@ocs.com.au \
--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®