mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Mingming cao <cmm@us.ibm.com>
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: Wed, 30 Jan 2002 05:26:43 +0300	[thread overview]
Message-ID: <20020130052643.5a0a8f61.johnpol@2ka.mipt.ru> (raw)
In-Reply-To: <3C575435.C123186@us.ibm.com>
In-Reply-To: <3C571DB2.4E0C0436@us.ibm.com> <20020130042025.051ee424.johnpol@2ka.mipt.ru> <3C575435.C123186@us.ibm.com>

On Tue, 29 Jan 2002 18:02:29 -0800
Mingming cao <cmm@us.ibm.com> wrote:

> 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......

As you mention md_compatible.h does not exist, it was introduced in 2.5.2
patch only in drivers/md/xor.c. But in at least pre5 all structures were
correctly defined in various md_{p,u,k}.h files. I've tried to find others
undefined symbols, but cann't. So i suggest you to upgrade a bit to pre6
or pre5 kernel ;), apply my litle patch and remove mention of
md_compatible.h in drivers/md/xor.c. And feel free to write all others
erorrs, if they will appear again.

> Thank you for your help.

Good luck.

> -- 
> Mingming Cao


	Evgeniy Polyakov ( s0mbre ).

      parent reply	other threads:[~2002-01-30  2:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-29 22:09 Mingming cao
2002-01-30  1:20 ` Evgeniy Polyakov
2002-01-30  2:02   ` Mingming cao
2002-01-30  2:26   ` Evgeniy Polyakov [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=20020130052643.5a0a8f61.johnpol@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --cc=cmm@us.ibm.com \
    --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

all inboxes | Powered by JetHome®