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, linux-kernel@vger.kernel.org,
	Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: linux-next: scsi tree build failure
Date: Mon, 15 Jun 2009 10:11:47 -0500	[thread overview]
Message-ID: <1245078707.3858.0.camel@mulgrave.site> (raw)
In-Reply-To: <20090615121716.c5bc0655.sfr@canb.auug.org.au>

On Mon, 2009-06-15 at 12:17 +1000, Stephen Rothwell wrote:
> Hi James,
> 
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
> 
> drivers/scsi/ps3rom.c: In function 'ps3rom_interrupt':
> drivers/scsi/ps3rom.c:302: error: implicit declaration of function 'ps3_system_bus_get_drvdata'
> drivers/scsi/ps3rom.c:302: warning: assignment makes pointer from integer without a cast
> drivers/scsi/ps3rom.c: In function 'ps3rom_probe':
> drivers/scsi/ps3rom.c:390: error: implicit declaration of function 'ps3_system_bus_set_drvdata'
> drivers/scsi/ps3rom.c: In function 'ps3rom_remove':
> drivers/scsi/ps3rom.c:421: warning: initialization makes pointer from integer without a cast
> 
> Caused by commit 4381bd58427116cd7689831998771ddd58078af9 ("[SCSI]
> ps3rom: Use ps3_system_bus_[gs]et_drvdata() instead of direct access").
> This is number 21 in a series and depends on number 19 which is not yet
> merged.  If you instead Ack this patch, Ben will merge it through the
> powerpc tree.
> 
> For today, I have used the scsi tree from next-20090612.

OK, dumped the offending patch, so it should be safe to take scsi-misc
again.

I'm so used to merging these type of conversions, I didn't check that it
was using a ps3 specific wrapper instead of a generic device one.

James

  reply	other threads:[~2009-06-15 15:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15  2:17 linux-next: scsi tree build failure Stephen Rothwell
2009-06-15 15:11 ` James Bottomley [this message]
2009-06-15 21:40   ` Benjamin Herrenschmidt
2009-06-16  2:24     ` James Bottomley
  -- strict thread matches above, loose matches on Subject: below --
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-12-15 14:37 Stephen Rothwell
2008-12-15 14:52 ` James Bottomley
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
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=1245078707.3858.0.camel@mulgrave.site \
    --to=james.bottomley@hansenpartnership.com \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=benh@kernel.crashing.org \
    --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).