From: NeilBrown <neilb@suse.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [md:for-next 18/18] dm-raid.c:(.text+0x11f6d5): undefined reference to `md_raid10_congested'
Date: Wed, 01 Aug 2012 21:17:49 +0000 [thread overview]
Message-ID: <20120802071749.50a7ea27@notabene.brown> (raw)
In-Reply-To: <20120801125102.GA19751@localhost>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
On Wed, 1 Aug 2012 10:33:07 -0500 Brassow Jonathan <jbrassow@redhat.com>
wrote:
>
> On Aug 1, 2012, at 7:51 AM, Fengguang Wu wrote:
>
> > Hi Jonathan,
> >
> > Kernel build failed on
> >
> > tree: git://neil.brown.name/md for-next
> > head: 63f33b8dda88923487004b20fba825486d009e7b
> > commit: 63f33b8dda88923487004b20fba825486d009e7b [18/18] DM RAID: Add support for MD RAID10
> > config: i386-randconfig-k016 (attached as .config)
> >
> > All related error/warning messages:
> >
> > drivers/built-in.o: In function `raid_is_congested':
> > dm-raid.c:(.text+0x11f6d5): undefined reference to `md_raid10_congested'
>
>
> Seems that the previous patches that this patch depends on are not applied in your case. Looking here:
> http://neil.brown.name/git?p=md;a=shortlog;h=refs/heads/for-next
> it seems that Neil has taken the prerequisites (in this case, "MD RAID10: export md_raid10_congested").
>
> brassow
We missed a bit:
config DM_RAID
tristate "RAID 1/4/5/6 target"
depends on BLK_DEV_DM
select MD_RAID1
select MD_RAID456
select BLK_DEV_MD
we need to add
select MD_RAID10
in there.
Thanks Fengguang!
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-08-01 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 12:51 [md:for-next 18/18] dm-raid.c:(.text+0x11f6d5): undefined reference to `md_raid10_congested' Fengguang Wu
2012-08-01 15:33 ` Brassow Jonathan
2012-08-01 21:17 ` NeilBrown [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=20120802071749.50a7ea27@notabene.brown \
--to=neilb@suse.de \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.