All of lore.kernel.org
 help / color / mirror / Atom feed
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 tree
Date: Wed, 28 Mar 2012 15:07:07 +1100	[thread overview]
Message-ID: <20120328150707.0e59c7c8@notabene.brown> (raw)
In-Reply-To: <20120328143204.134662a493ade33ddd523821@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 676 bytes --]

On Wed, 28 Mar 2012 14:32:04 +1100 Stephen Rothwell <sfr@canb.auug.org.au>
wrote:

> Hi Neil,
> 
> After merging the md tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
> 
> drivers/md/raid5.c: In function 'analyse_stripe':
> drivers/md/raid5.c:3209:33: error: 'struct stripe_head' has no member named 'devs'
> 
> Caused by commit 85e25cfc6bed ("md/raid5: fix handling of bad blocks
> during recovery").
> 
> I have used the version of the md tree from next-20120327 for today.

Sorry 'bout that.  I noticed not long after I had pushed out for-next and
fixed it.  You must have pulled during that window :-(

Thanks,
NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-03-28  4:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28  3:32 linux-next: build failure after merge of the md tree Stephen Rothwell
2012-03-28  3:32 ` Stephen Rothwell
2012-03-28  4:07 ` NeilBrown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-06-22  1:44 Stephen Rothwell
2017-07-03  1:52 ` Stephen Rothwell
2017-06-14  1:58 Stephen Rothwell
2015-03-02  5:50 Stephen Rothwell
2015-03-02  6:03 ` NeilBrown
2015-03-02  6:11   ` Stephen Rothwell
2015-03-03  2:35     ` Stephen Rothwell
2015-03-04  2:44       ` NeilBrown
2015-03-04  2:48         ` Stephen Rothwell
2015-03-13  8:55       ` Guoqing Jiang
2012-09-25  3:31 Stephen Rothwell
2012-09-25  4:10 ` NeilBrown
2012-09-25  4:50   ` Stephen Rothwell
2012-04-19  2:55 Stephen Rothwell
2012-04-19  3:15 ` NeilBrown
2012-04-11  3:42 Stephen Rothwell
2012-04-11  3:54 ` H. Peter Anvin
2012-04-11  4:48 ` NeilBrown
2011-10-11  5:29 Stephen Rothwell
2011-10-11  5:42 ` NeilBrown
2011-10-07  3:07 Stephen Rothwell
2011-10-07  3:34 ` NeilBrown

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=20120328150707.0e59c7c8@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 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.