All of lore.kernel.org
 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,
	"David S. Miller" <davem@davemloft.net>,
	Jaswinder Singh <jaswinder@infradead.org>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: linux-next: scsi tree build failure
Date: Tue, 30 Dec 2008 10:30:31 -0600	[thread overview]
Message-ID: <1230654631.3296.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20081231031639.dc19a03c.sfr@canb.auug.org.au>

On Wed, 2008-12-31 at 03:16 +1100, Stephen Rothwell wrote:
> Hi James,
> 
> Today's linux-next build (sparc defconfig) failed like this:
> 
> drivers/scsi/qlogicpti.c: In function 'qlogicpti_load_firmware':
> drivers/scsi/qlogicpti.c:480: error: 'struct qlogicpti' has no member named 'sdev'
> 
> An interaction between commit 68175399c8b5ee90960e78c1bb8e3353e71fbf33
> ("[SCSI] qlogicpti: use request_firmware") from the scsi tree and commit
> 5dc2536bb8d8adb5fdfbe76cd6fdcdf9de3f40f8 ("qlogicpti: Convert to pure OF
> driver") which is in Linus' tree.
> 
> The version of the firmware commit that has been in the firmware tree
> since Nov 19 has this conflict corrected.
> 
> I have left it for today (as it is getting way to late).  Please fix it
> up for tomorrow.

I'm slightly annoyed this hasn't been building.  I accepted it into the
SCSI tree because I was under the impression it had been well tested in
linux-next.

I can't actually build this driver, but I think this is the fix, if
someone can verify, I'll fold it into the patch.

Looking at the firmware patches, they all seem to have a kconfig
deficiency in that the modified drivers should now be selecting
FW_LOADER ... it this the case?

James

---

diff --git a/drivers/scsi/qlogicpti.c b/drivers/scsi/qlogicpti.c
index e17a4d2..a342426 100644
--- a/drivers/scsi/qlogicpti.c
+++ b/drivers/scsi/qlogicpti.c
@@ -477,7 +477,7 @@ static int __devinit qlogicpti_load_firmware(struct qlogicpti *qpti)
 	unsigned long flags;
 	int i, timeout;
 
-	err = request_firmware(&fw, FIRMWARE_1000, &qpti->sdev->ofdev.dev);
+	err = request_firmware(&fw, FIRMWARE_1000, &qpti->op->dev);
 	if (err) {
 		printk(KERN_ERR "Failed to load image \"%s\" err %d\n",
 		       FIRMWARE_1000, err);

  reply	other threads:[~2008-12-30 16:30 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30 16:16 linux-next: scsi tree build failure Stephen Rothwell
2008-12-30 16:30 ` James Bottomley [this message]
  -- 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-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 12:25 ` Stephen Rothwell
2008-07-07 14:39 ` James Bottomley
2008-07-07 14:39   ` James Bottomley
2008-07-07 14:53   ` Robert Jennings
2008-07-07 14:53     ` Robert Jennings
2008-07-07 22:05   ` Benjamin Herrenschmidt
2008-07-07 22:05     ` Benjamin Herrenschmidt
2008-07-07 22:07     ` James Bottomley
2008-07-07 22:07       ` James Bottomley
2008-07-07 22:48       ` Benjamin Herrenschmidt
2008-07-07 22:48         ` Benjamin Herrenschmidt
2008-07-07 22:00 ` 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=1230654631.3296.13.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=davem@davemloft.net \
    --cc=jaswinder@infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-scsi@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.