From: "Mike Black" <mblack@csi-inc.com>
To: "Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: linux 2.5.23
Date: Wed, 19 Jun 2002 10:47:25 -0400 [thread overview]
Message-ID: <041c01c217a0$3aa34520$f6de11cc@black> (raw)
In-Reply-To: Pine.LNX.4.33.0206181915001.1773-100000@penguin.transmeta.com
Hmmm...looks like ITERATE_MDDEV interaction with _raw_spin_lock is hosed....I dont' quite see the problem
Line 754 is:
ITERATE_MDDEV(mddev,tmp) {
gcc -Wp,-MD,./.md.o.d -D__KERNEL__ -I/usr/src/linux-2.5.23/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-point
er -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -nostdinc -iwithprefix include -DKBUILD_BASENA
ME=md -DEXPORT_SYMTAB -c -o md.o md.c
md.c: In function `md_print_devices':
md.c:754: parse error before `do'
md.c:748: warning: unused variable `mddev'
md.c:747: warning: unused variable `rdev'
md.c:746: warning: unused variable `tmp2'
md.c:746: warning: unused variable `tmp'
md.c: At top level:
md.c:754: parse error before `while'
md.c:754: parse error before `&'
md.c:754: warning: type defaults to `int' in declaration of `_raw_spin_lock'
md.c:754: warning: function declaration isn't a prototype
md.c:754: conflicting types for `_raw_spin_lock'
/usr/src/linux-2.5.23/include/asm/spinlock.h:117: previous declaration of `_raw_spin_lock'
md.c:754: warning: data definition has no type or storage class
md.c:754: parse error before `&'
md.c:754: warning: type defaults to `int' in declaration of `_raw_spin_lock'
md.c:754: warning: function declaration isn't a prototype
md.c:754: warning: data definition has no type or storage class
md.c:757: warning: type defaults to `int' in declaration of `rdev'
next prev parent reply other threads:[~2002-06-19 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-19 2:18 linux 2.5.23 Linus Torvalds
2002-06-19 14:47 ` Mike Black [this message]
2002-06-20 13:38 ` Martin Dalecki
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='041c01c217a0$3aa34520$f6de11cc@black' \
--to=mblack@csi-inc.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