public inbox for linux-next@vger.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
Subject: Re: linux-next: md tree build failure
Date: Tue, 10 Mar 2009 17:38:19 +1100 (EST)	[thread overview]
Message-ID: <d7e2f37be5a29b90440a7a4780327b0f.squirrel@neil.brown.name> (raw)
In-Reply-To: <20090310164750.affe762c.sfr@canb.auug.org.au>

On Tue, March 10, 2009 4:47 pm, Stephen Rothwell wrote:
> Hi Neil,
>
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
>
> drivers/md/raid10.c: In function 'sync_request':
> drivers/md/raid10.c:1753: error: implicit declaration of function
> 'msleep_interruptible'
>
> Caused by commit 10d4564a71c58e89ddee656eb6cb0fecf5ac4b3c ("md: move lots
> of #include lines out of .h files and into .c").
>
> I have merged the version of the md tree fomr next-20090306 instead of
> today's.

Thanks.
I've fixed this now so you should get more happiness next time.

NeilBrown

  reply	other threads:[~2009-03-10  6:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10  5:47 linux-next: md tree build failure Stephen Rothwell
2009-03-10  6:38 ` NeilBrown [this message]
2009-03-10  6:48   ` 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-11  5:27 Stephen Rothwell
2009-03-13  0:45 ` Neil Brown
2009-03-13  2:21   ` 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=d7e2f37be5a29b90440a7a4780327b0f.squirrel@neil.brown.name \
    --to=neilb@suse$(echo .)de \
    --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