From: Adrian Bunk <bunk@fs.tum.de>
To: James Bottomley <james.bottomley@steeleye.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.5.60: sim710.c doesn't compile
Date: Tue, 11 Feb 2003 19:16:00 +0100 [thread overview]
Message-ID: <20030211181600.GP17128@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0302101103570.1348-100000@penguin.transmeta.com>
On Mon, Feb 10, 2003 at 11:08:28AM -0800, Linus Torvalds wrote:
>...
> Summary of changes from v2.5.59 to v2.5.60
> ============================================
>...
> James Bottomley <james.bottomley@steeleye.com>:
>...
> o [SCSI] Migrate sim710 to 53c700 chip driver
>...
This change broke the compilation of sim710.c:
<-- snip -->
...
gcc -Wp,-MD,drivers/scsi/.sim710.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=sim710 -DKBUILD_MODNAME=sim710 -c -o
drivers/scsi/sim710.o drivers/scsi/sim710.c
drivers/scsi/sim710.c:329: `sim710_device_remove' undeclared here (not in a function)
drivers/scsi/sim710.c:329: initializer element is not constant
drivers/scsi/sim710.c:329: (near initialization for `sim710_eisa_driver.driver.remove')
drivers/scsi/sim710.c:330: initializer element is not constant
drivers/scsi/sim710.c:330: (near initialization for `sim710_eisa_driver.driver')
make[2]: *** [drivers/scsi/sim710.o] Error 1
<-- snip -->
This is the only occurence of sim710_device_remove in the whole kernel
tree.
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:[~2003-02-11 18:06 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 19:08 Linux 2.5.60 Linus Torvalds
2003-02-10 20:41 ` Maciej Soltysiak
2003-02-10 21:06 ` Linux 2.5.60 Compile error James Lamanna
2003-02-10 21:38 ` Kevin Corry
2003-02-10 22:50 ` Muli Ben-Yehuda
2003-02-10 21:52 ` Dave Jones
2003-02-11 0:12 ` Another " Vlad@geekizoid.com
2003-02-11 5:21 ` Anthony J. Breeds-Taurima
2003-02-10 21:11 ` Linux 2.5.60 Stephen Hemminger
2003-02-10 21:25 ` James Lamanna
2003-02-10 22:54 ` Linus Torvalds
2003-02-10 20:46 ` 2.5.60: JFS no longer compiles with gcc 2.95 Adrian Bunk
2003-02-10 21:43 ` James Lamanna
2003-02-11 7:27 ` Adrian Bunk
2003-02-12 14:52 ` [PATCH - 2.5.60] " Dave Kleikamp
2003-02-12 15:04 ` Adrian Bunk
2003-02-12 15:42 ` Dave Kleikamp
2003-02-12 16:22 ` Andreas Schwab
2003-02-10 22:21 ` Linux 2.5.60 John Cherry
2003-02-11 7:08 ` Oleg Drokin
2003-02-11 7:38 ` Linus Torvalds
2003-02-12 8:11 ` Eric W. Biederman
2003-02-12 11:49 ` Jeff Dike
2003-02-13 23:25 ` Werner Almesberger
2003-02-11 15:16 ` Zephaniah E. Hull
2003-02-11 22:47 ` Andrew Morton
2003-02-11 22:54 ` Andrew Morton
2003-02-14 16:56 ` Zephaniah E. Hull
2003-02-11 16:23 ` Russell King
2003-02-11 17:06 ` Linus Torvalds
2003-02-12 2:47 ` David S. Miller
2003-02-11 16:44 ` 2.5.60: arlan.c no longer compiles Adrian Bunk
2003-02-11 23:08 ` Andrew Morton
2003-02-11 18:16 ` Adrian Bunk [this message]
2003-02-11 18:21 ` 2.5.60: sim710.c doesn't compile James Bottomley
2003-02-11 22:00 ` Linux 2.5.60 Rudmer van Dijk
2003-02-12 10:05 ` Ingo Oeser
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=20030211181600.GP17128@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=james.bottomley@steeleye.com \
--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