From: NeilBrown <neilb@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the md-current tree
Date: Wed, 2 Feb 2011 11:58:13 +1100 [thread overview]
Message-ID: <20110202115813.1ee7ab4d@notabene.brown> (raw)
In-Reply-To: <20110202112519.7a4d2bd3.sfr@canb.auug.org.au>
On Wed, 2 Feb 2011 11:25:19 +1100 Stephen Rothwell <sfr@canb.auug.org.au>
wrote:
> Hi Neil,
>
> After merging the md-current tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> drivers/md/md.c: In function 'slot_store':
> drivers/md/md.c:2466: error: 'mddev' undeclared (first use in this function)
>
> Caused by commit 778f14598b2924e92790ddd8a167424d2894ffb0 ("md: Don't
> allow slot_store while resync/recovery is happening").
>
> Please build test your tree before publishing it.
>
> I have used the md-current tree from next-20110201 for today.
>
Ouch... I blame the heat!!
Fix now, thanks.
NeilBrown
prev parent reply other threads:[~2011-02-02 0:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 0:25 linux-next: build failure after merge of the md-current tree Stephen Rothwell
2011-02-02 0:58 ` 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=20110202115813.1ee7ab4d@notabene.brown \
--to=neilb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).