From: Adrian Bunk <bunk@fs.tum.de>
To: Linus Torvalds <torvalds@transmeta.com>,
Doug Ledford <dledford@aladin.rdu.redhat.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.5.50
Date: Sun, 1 Dec 2002 15:41:02 +0100 [thread overview]
Message-ID: <20021201144102.GF29084@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0211271456160.18214-100000@penguin.transmeta.com>
On Wed, Nov 27, 2002 at 03:07:38PM -0800, Linus Torvalds wrote:
>...
> Summary of changes from v2.5.49 to v2.5.50
> ============================================
>...
> Doug Ledford <dledford@aladin.rdu.redhat.com>:
>...
> o Convert from host->host_queue to host->my_devices list usage Add in
> usage of new same_target_siblings list Add
> scsi_release_commandblocks() call to scsi_free_sdev() Make all scsi
> device freeing use scsi_free_sdev()
>...
The change to eata_pio_proc.c contains a typo:
<-- snip -->
...
gcc -Wp,-MD,drivers/scsi/.eata_pio.o.d -D__KERNEL__ -Iinclude -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=k6 -Iarch/i386/mach-generic
-nostdinc -iwithprefix include -DKBUILD_BASENAME=eata_pio
-DKBUILD_MODNAME=eata_pio
-c -o drivers/scsi/eata_pio.o drivers/scsi/eata_pio.c
In file included from drivers/scsi/eata_pio.c:94:
drivers/scsi/eata_pio_proc.c:88: macro `list_for_each_entry' used with only 2 args
In file included from drivers/scsi/eata_pio.c:94:
drivers/scsi/eata_pio_proc.c: In function `eata_pio_proc_info':
drivers/scsi/eata_pio_proc.c:88: parse error before `)'
...
make[2]: *** [drivers/scsi/eata_pio.o] Error 1
<-- snip -->
The fix is simple:
--- linux-2.5.50/drivers/scsi/eata_pio_proc.c.old 2002-12-01 15:32:22.000000000 +0100
+++ linux-2.5.50/drivers/scsi/eata_pio_proc.c 2002-12-01 15:32:50.000000000 +0100
@@ -85,7 +85,7 @@
len += size;
pos = begin + len;
- list_for_each_entry(scd, &HBA_ptr->my_devices; siblings) {
+ list_for_each_entry(scd, &HBA_ptr->my_devices, siblings) {
proc_print_scsidevice(scd, buffer, &size, len);
len += size;
pos = begin + len;
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
prev parent reply other threads:[~2002-12-01 14:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 23:07 Linux v2.5.50 Linus Torvalds
2002-11-28 0:49 ` Udo A. Steinberg
2002-11-28 9:10 ` Gerd Knorr
2002-11-28 11:35 ` Gerd Knorr
2002-11-28 2:43 ` [uPATCH] NCR5380.c compile fix " Paul
2002-12-04 10:52 ` Geert Uytterhoeven
2002-11-28 4:55 ` [oops] BUG at mm/highmem.c:455 " Paul
2002-11-28 4:57 ` Nathan Walp
2002-11-28 10:15 ` drivers/pci/quirks.c / " Sebastian Benoit
2002-11-28 16:25 ` Alan Cox
2002-11-28 17:02 ` Ivan Kokshaysky
2002-11-28 17:30 ` Dave Jones
2002-11-28 18:54 ` Alan Cox
2002-11-28 18:25 ` Dave Jones
2002-11-28 18:30 ` Mike Dresser
2002-11-28 17:41 ` Alan Cox
2002-11-28 17:31 ` Dave Jones
2002-11-28 17:41 ` Ivan Kokshaysky
2002-11-28 13:17 ` Geert Uytterhoeven
2002-11-30 20:06 ` Adrian Bunk
2002-12-01 14:41 ` Adrian Bunk [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=20021201144102.GF29084@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=dledford@aladin.rdu.redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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