From: Adrian Bunk <bunk@fs.tum.de>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
info@formula-n.de, kronos@kronoz.cjb.net
Cc: linux-kernel@vger.kernel.org, kkeil@suse.de,
kai.germaschewski@gmx.de, isdn4linux@listserv.isdn4linux
Subject: [patch] 2.4.25-rc1: amd7930_fn doesn't compile
Date: Fri, 6 Feb 2004 19:01:44 +0100 [thread overview]
Message-ID: <20040206180144.GF26093@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.58L.0402051037190.9788@logos.cnet>
On Thu, Feb 05, 2004 at 10:44:31AM -0200, Marcelo Tosatti wrote:
>...
> Summary of changes from v2.4.25-pre8 to v2.4.25-rc1
> ============================================
>...
> Luca Tettamanti:
>...
> o Fix amd7930_fn.h compilation warning
>...
This causes the following compile error when trying to compile this
driver statically into a kernel with CONFIG_HOTPLUG=n :
<-- snip -->
...
gcc -D__KERNEL__
-I/home/bunk/linux/kernel-2.4/linux-2.4.25-rc1-full-no-hotplug/include
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
-fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2
-march=athlon -DHISAX_MAX_CARDS=8 -nostdinc -iwithprefix include
-DKBUILD_BASENAME=amd7930_fn -c -o amd7930_fn.o amd7930_fn.c
amd7930_fn.c: In function `Amd7930_init':
amd7930_fn.c:752: error: Amd7930_init causes a section type conflict
{standard input}: Assembler messages:
{standard input}:2: Warning: setting incorrect section attributes for .text.init
make[4]: *** [amd7930_fn.o] Error 1
make[4]: Leaving directory `/home/bunk/linux/kernel-2.4/linux-2.4.25-rc1-full-no-hotplug/drivers/isdn/hisax'
<-- snip -->
The fix is obvious:
--- linux-2.4.25-rc1-full-no-hotplug/drivers/isdn/hisax/amd7930_fn.c.old 2004-02-06 00:37:28.000000000 +0100
+++ linux-2.4.25-rc1-full-no-hotplug/drivers/isdn/hisax/amd7930_fn.c 2004-02-06 00:37:56.000000000 +0100
@@ -61,7 +61,7 @@
#include <linux/interrupt.h>
#include <linux/init.h>
-static WORD initAMD[] __devinit = {
+static WORD initAMD[] __devinitdata = {
0x0100,
0x00A5, 3, 0x01, 0x40, 0x58, // LPR, LMR1, LMR2
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:[~2004-02-06 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 12:44 Linux 2.4.25-rc1 Marcelo Tosatti
2004-02-06 18:01 ` Adrian Bunk [this message]
2004-02-29 4:44 ` David Luyer
2004-03-01 15:16 ` Marcelo Tosatti
2004-03-01 15:20 ` Rik van Riel
2004-03-01 23:38 ` David Luyer
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=20040206180144.GF26093@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=info@formula-n.de \
--cc=isdn4linux@listserv.isdn4linux \
--cc=kai.germaschewski@gmx.de \
--cc=kkeil@suse.de \
--cc=kronos@kronoz.cjb.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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
all inboxes | Powered by JetHome®