From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: linux-next@vger.kernel.org,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: linux-next: driver-core build failure
Date: Thu, 17 Jul 2008 10:32:07 +1000 [thread overview]
Message-ID: <20080717103207.ccced1ca.sfr@canb.auug.org.au> (raw)
Hi Greg,
I have been carrying the patch below and applying it after the scsi tree
merge for some time now. Now that the scsi tree has been merged into
Linus' tree, can you add this to the driver-core tree, please?
Preferably merged with the patch that changes the class_find_device API.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
>From 66bcc1fea773190ed16597c1b57b9a8601ba1a23 Mon Sep 17 00:00:00 2001
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 6 Jun 2008 14:26:18 +1000
Subject: [PATCH] scsi: fix fallout from the class_find_device API change
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
drivers/scsi/scsi_transport_iscsi.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/scsi_transport_iscsi.c b/drivers/scsi/scsi_transport_iscsi.c
index 7794651..5ce9151 100644
--- a/drivers/scsi/scsi_transport_iscsi.c
+++ b/drivers/scsi/scsi_transport_iscsi.c
@@ -170,7 +170,7 @@ iscsi_create_endpoint(int dd_size)
int err;
for (id = 1; id < ISCSI_MAX_EPID; id++) {
- dev = class_find_device(&iscsi_endpoint_class, &id,
+ dev = class_find_device(&iscsi_endpoint_class, NULL, &id,
iscsi_match_epid);
if (!dev)
break;
@@ -221,7 +221,7 @@ struct iscsi_endpoint *iscsi_lookup_endpoint(u64 handle)
{
struct device *dev;
- dev = class_find_device(&iscsi_endpoint_class, &handle,
+ dev = class_find_device(&iscsi_endpoint_class, NULL, &handle,
iscsi_match_epid);
if (!dev)
return NULL;
--
1.5.5.3
next reply other threads:[~2008-07-17 0:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 0:32 Stephen Rothwell [this message]
2008-07-17 7:04 ` linux-next: driver-core build failure Greg KH
-- strict thread matches above, loose matches on Subject: below --
2008-07-17 0:36 Stephen Rothwell
2008-07-17 7:04 ` Greg KH
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=20080717103207.ccced1ca.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=James.Bottomley@HansenPartnership.com \
--cc=greg@kroah.com \
--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;
as well as URLs for NNTP newsgroup(s).