From: Stephen Rothwell <sfr@canb.auug.org.au>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: linux-next: scsi tree build failure
Date: Mon, 15 Jun 2009 12:17:16 +1000 [thread overview]
Message-ID: <20090615121716.c5bc0655.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
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.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-06-15 2:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 2:17 Stephen Rothwell [this message]
2009-06-15 15:11 ` James Bottomley
2009-06-15 21:40 ` Benjamin Herrenschmidt
2009-06-16 2:24 ` James Bottomley
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=20090615121716.c5bc0655.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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
all inboxes | Powered by JetHome®