public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mingming cao <cmm@us.ibm.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Could not compile md/raid5.c and md/multipath.c in 2.5.3-pre3
Date: Tue, 29 Jan 2002 14:09:54 -0800	[thread overview]
Message-ID: <3C571DB2.4E0C0436@us.ibm.com> (raw)

Hello,

While compiling the clean 2.5.3-pre3 kernel I found the
drivers/md/raid5.c and drivers/md/multipatch.c could not get compiled.
Here is the compiling error for raid5.c: 

......
-D__KERNEL__ -I/home/ming/views/253-pre3/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686    -c -o raid5.o raid5.c
In file included from raid5.c:23:
/home/ming/views/253-pre3/include/linux/raid/raid5.h:218: parse error
before `md_wait_queue_head_t'
/home/ming/views/253-pre3/include/linux/raid/raid5.h:218: warning: no
semicolon
at end of struct or union
/home/ming/views/253-pre3/include/linux/raid/raid5.h:222: parse error
before `device_lock'
......


This failure also happened for 2.5.2 kernel.  Both of raid5.c and
multipatch.c use some data structures defined in md_compatible.h, which
was included in md.h before but does not exist under include/linux/raid
for now.  Could someone fix this?



-- 
Mingming Cao

             reply	other threads:[~2002-01-29 22:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-29 22:09 Mingming cao [this message]
2002-01-30  1:20 ` Could not compile md/raid5.c and md/multipath.c in 2.5.3-pre3 Evgeniy Polyakov
2002-01-30  2:02   ` Mingming cao
2002-01-30  2:26     ` Evgeniy Polyakov

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=3C571DB2.4E0C0436@us.ibm.com \
    --to=cmm@us.ibm.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