From: Miles Bader <miles@lsi.nec.co.jp>
To: linux-kernel@vger.kernel.org
Subject: 2.5.45: drivers/mtd/mtdblock.c won't compile -- misordered declaration
Date: 01 Nov 2002 14:24:13 +0900 [thread overview]
Message-ID: <buod6ppj20y.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
When I compile 2.5.45, I get the following errors:
v850e-elf-gcc -Wp,-MD,drivers/mtd/.mtdblock.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -g -fomit-frame-pointer -fno-strict-aliasing -fno-common -mv850e -ffixed-r16 -mno-prolog-function -fno-builtin -D__linux__ -DUTS_SYSNAME=\"uClinux\" -nostdinc -iwithprefix include -DKBUILD_BASENAME=mtdblock -c -o drivers/mtd/mtdblock.o drivers/mtd/mtdblock.c
drivers/mtd/mtdblock.c:398: parse error before `struct'
drivers/mtd/mtdblock.c:399: `p' undeclared (first use in this function)
I fixed this locally as follows:
diff -ruN -X../cludes ../orig/linux-2.5.45-uc1/drivers/mtd/mtdblock.c drivers/mtd/mtdblock.c
--- ../orig/linux-2.5.45-uc1/drivers/mtd/mtdblock.c 2002-10-31 11:41:04.000000000 +0900
+++ drivers/mtd/mtdblock.c 2002-11-01 12:43:26.000000000 +0900
@@ -393,9 +393,10 @@
unsigned int res;
while (!blk_queue_empty(&mtd_queue)) {
+ struct mtdblk_dev **p;
struct request *req = elv_next_request(&mtd_queue);
spin_unlock_irq(mtd_queue.queue_lock);
- struct mtdblk_dev **p = req->rq_disk->private_data;
+ p = req->rq_disk->private_data;
mtdblk = *p;
res = 0;
Thanks,
-Miles
--
Quidquid latine dictum sit, altum viditur.
next reply other threads:[~2002-11-01 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 5:24 Miles Bader [this message]
2002-11-05 4:45 ` 2.5.46: " Miles Bader
2002-11-05 9:18 ` Russell King
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=buod6ppj20y.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.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®