linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Robert Love <robert.w.love@intel.com>
Subject: Re: linux-next: scsi tree build failure
Date: Mon, 15 Dec 2008 08:52:42 -0600	[thread overview]
Message-ID: <1229352762.3293.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20081216013704.2496da40.sfr@canb.auug.org.au>

On Tue, 2008-12-16 at 01:37 +1100, Stephen Rothwell wrote:
> Hi James,
> 
> Today's linux-next build (powerpc allyesconfig) failed like this:

Heh, I really need to get this terrasoft system integrated into my
builds

> drivers/scsi/libfc/fc_fcp.c: In function 'fc_eh_host_reset':
> drivers/scsi/libfc/fc_fcp.c:1987: error: implicit declaration of function 'msleep'
> 
> That file needs to include <linux/delay.h>.

Thanks, that's exactly the problem.

Robert, please reroll the patches with this fix in ... I'll just
exchange the new patches for the ones in my tree.

> Introduced by commit 389571f347629d879f9044582bbbafb43e4fe00b ("[SCSI]
> libfc: A modular Fibre Channel library") from the scsi tree.  I reverted
> that commit and commit 7aba33c5cfc7a9c104cc7469558c7849f373c3da ("[SCSI]
> fcoe: Fibre Channel over Ethernet") which depended on it.

James

  reply	other threads:[~2008-12-15 14:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15 14:37 linux-next: scsi tree build failure Stephen Rothwell
2008-12-15 14:52 ` James Bottomley [this message]
2008-12-17 12:20   ` Stephen Rothwell
2008-12-21  3:30     ` Stephen Rothwell
2008-12-22  1:59       ` James Bottomley
2008-12-22  2:38         ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-06-15  2:17 Stephen Rothwell
2009-06-15 15:11 ` James Bottomley
2009-06-15 21:40   ` Benjamin Herrenschmidt
2009-06-16  2:24     ` James Bottomley
2009-04-02  5:49 Stephen Rothwell
2009-04-02 14:22 ` James Bottomley
2009-04-02 17:19   ` Robert Love
2009-04-02 18:23     ` James Bottomley
2009-04-03  0:26       ` Stephen Rothwell
2009-04-03  1:16         ` James Bottomley
2009-04-03  2:37           ` Stephen Rothwell
2009-03-16 10:39 Stephen Rothwell
2009-03-16 13:22 ` James Bottomley
2008-12-30 16:16 Stephen Rothwell
2008-12-30 16:30 ` James Bottomley
2008-10-15  6:49 Stephen Rothwell
2008-10-15 12:27 ` James Bottomley
2008-07-07 12:25 Stephen Rothwell
2008-07-07 14:39 ` James Bottomley
2008-07-07 14:53   ` Robert Jennings
2008-07-07 22:05   ` Benjamin Herrenschmidt
2008-07-07 22:07     ` James Bottomley
2008-07-07 22:48       ` Benjamin Herrenschmidt
2008-07-07 22:00 ` Benjamin Herrenschmidt

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=1229352762.3293.1.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-next@vger.kernel.org \
    --cc=robert.w.love@intel.com \
    --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).