From: Mingming cao <cmm@us.ibm.com>
To: johnpol@2ka.mipt.ru
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
linux-raid@vger.kernel.org
Subject: Re: Could not compile md/raid5.c and md/multipath.c in 2.5.3-pre3
Date: Tue, 29 Jan 2002 18:02:29 -0800 [thread overview]
Message-ID: <3C575435.C123186@us.ibm.com> (raw)
In-Reply-To: <3C571DB2.4E0C0436@us.ibm.com> <20020130042025.051ee424.johnpol@2ka.mipt.ru>
Evgeniy Polyakov wrote:
>
> On Tue, 29 Jan 2002 14:09:54 -0800
> Mingming cao <cmm@us.ibm.com> wrote:
>
> > Hello,
>
> Good time of day.
>
> > -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'
> > ......
> > for now. Could someone fix this?
>
> I hope this patch will help you.
>
> This patch is also cc'ed to Ingo Molnar, who is one of the maintainers of
> multiple discs support. Is it right, Ingo?
> Or noone should annoy anyone with such things?
>
Hello Evgeniy,
I omitted similar compile errors in the last email. raid5.c and
multipath.c referenced a lot data structures defined in
md_compatible.h, besides the two you added in your fix......
Thank you for your help.
--
Mingming Cao
IBM Linux Technology Center
503-578-5024 IBM T/L: 775-5024
cmm@us.ibm.com
http://www.ibm.com/linux/ltc
next prev parent reply other threads:[~2002-01-30 2:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-29 22:09 Could not compile md/raid5.c and md/multipath.c in 2.5.3-pre3 Mingming cao
2002-01-30 1:20 ` Evgeniy Polyakov
2002-01-30 2:02 ` Mingming cao [this message]
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=3C575435.C123186@us.ibm.com \
--to=cmm@us.ibm.com \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mingo@redhat.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