From: Neil Brown <neilb@suse•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, Dan Williams <dan.j.williams@intel•com>
Subject: Re: linux-next: md tree build failure
Date: Fri, 13 Mar 2009 11:45:59 +1100 [thread overview]
Message-ID: <18873.44231.864323.344008@notabene.brown> (raw)
In-Reply-To: message from Stephen Rothwell on Wednesday March 11
On Wednesday March 11, sfr@canb•auug.org.au wrote:
> Hi Neil,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> ERROR: "raid6_empty_zero_page" [drivers/md/raid456.ko] undefined!
> ERROR: "raid6_empty_zero_page" [crypto/async_tx/async_pq.ko] undefined!
>
> Maybe caused by commit 4739d067d35c26093f4ba29a716ce9d60c36dc53
> ("md/raid5: move raid6 data processing to raid6_pq.ko")?
>
> I have merged the version of the md tree from next-20090306 for today.
Thanks.
I've export raid6_empty_zero_page. I think that is the correct fix.
So Monday should be a winner :-)
NeilBrown
next prev parent reply other threads:[~2009-03-13 0:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 5:27 linux-next: md tree build failure Stephen Rothwell
2009-03-13 0:45 ` Neil Brown [this message]
2009-03-13 2:21 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-05-25 5:33 Stephen Rothwell
2009-05-25 6:15 ` Jens Axboe
2009-05-25 11:44 ` Martin K. Petersen
2009-06-01 4:42 ` Stephen Rothwell
2009-06-01 5:13 ` Martin K. Petersen
2009-06-01 5:33 ` NeilBrown
[not found] ` <yq1prdm6jn1.fsf@sermon.lab.mkp.net>
2009-06-04 4:06 ` Neil Brown
2009-06-04 4:17 ` Martin K. Petersen
2009-03-10 5:47 Stephen Rothwell
2009-03-10 6:38 ` NeilBrown
2009-03-10 6:48 ` Stephen Rothwell
2008-10-15 9:09 Stephen Rothwell
2008-10-15 10:55 ` Neil Brown
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=18873.44231.864323.344008@notabene.brown \
--to=neilb@suse$(echo .)de \
--cc=dan.j.williams@intel$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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