From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: yoshfuji@linux-ipv6.org, "David S. Miller" <davem@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.5.69-bk7: wireless.c must include module.h
Date: Mon, 12 May 2003 15:24:16 -0700 [thread overview]
Message-ID: <20030512222416.GA26396@bougret.hpl.hp.com> (raw)
In-Reply-To: <20030512220512.GC1107@fs.tum.de>
On Tue, May 13, 2003 at 12:05:12AM +0200, Adrian Bunk wrote:
> <-- snip -->
>
> ...
> gcc -Wp,-MD,net/core/.wireless.o.d -D__KERNEL__ -Iinclude -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> -pipe -mpreferred-stack-boundary=2 -march=k6
> -Iinclude/asm-i386/mach-default -nostdinc -iwithprefix include
> -DKBUILD_BASENAME=wireless -DKBUILD_MODNAME=wireless -c -o
> net/core/wireless.o net/core/wireless.c
> net/core/wireless.c:488: `THIS_MODULE' undeclared here (not in a function)
> net/core/wireless.c:488: initializer element is not constant
> net/core/wireless.c:488: (near initialization for `wireless_seq_fops.owner')
> make[2]: *** [net/core/wireless.o] Error 1
>
> <-- snip -->
>
>
> The fix is simple:
>
> --- linux-2.5.69-bk7/net/core/wireless.c.old 2003-05-13 00:02:06.000000000 +0200
> +++ linux-2.5.69-bk7/net/core/wireless.c 2003-05-13 00:02:42.000000000 +0200
> @@ -60,6 +60,7 @@
> #include <linux/seq_file.h>
> #include <linux/init.h> /* for __init */
> #include <linux/if_arp.h> /* ARPHRD_ETHER */
> +#include <linux/module.h>
>
> #include <linux/wireless.h> /* Pretty obvious */
> #include <net/iw_handler.h> /* New driver API */
>
>
>
> cu
> Adrian
I still managed to beat you by a few minute ;-)
http://marc.theaimsgroup.com/?l=linux-kernel&m=105276406917601&w=2
Thanks !
Jean
prev parent reply other threads:[~2003-05-12 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 22:05 [patch] 2.5.69-bk7: wireless.c must include module.h Adrian Bunk
2003-05-12 21:12 ` David S. Miller
2003-05-12 22:24 ` Jean Tourrilhes [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=20030512222416.GA26396@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=bunk@fs.tum.de \
--cc=davem@redhat.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).