From: James Bottomley <James.Bottomley@SteelEye.com>
To: Frederik Deweerdt <deweerdt@free.fr>
Cc: jens.axboe@oracle.com, fujita.tomonori@lab.ntt.co.jp,
linux-kernel@vger.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [patch] drivers/scsi/scsi_sysfs.c:718: warning: unused variable `rq'
Date: Mon, 23 Jul 2007 09:53:51 -0500 [thread overview]
Message-ID: <1185202432.3417.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20070723143637.GB23448@slug>
On Mon, 2007-07-23 at 16:36 +0200, Frederik Deweerdt wrote:
> - struct request_queue *rq = sdev->request_queue;
>
> if ((error = scsi_device_set_state(sdev, SDEV_RUNNING)) != 0)
> return error;
> @@ -736,7 +735,8 @@ int scsi_sysfs_add_sdev(struct scsi_device *sdev)
> * released by the sdev_class .release */
> get_device(&sdev->sdev_gendev);
>
> - error = bsg_register_queue(rq, &sdev->sdev_gendev, NULL);
> + error = bsg_register_queue(sdev->request_queue,
> + &sdev->sdev_gendev, NULL);
Actually, that's not really a good fix because the same problem will
reoccur elsewhere. This is a more correct fix:
James
diff --git a/include/linux/bsg.h b/include/linux/bsg.h
index f415f89..2344dab 100644
--- a/include/linux/bsg.h
+++ b/include/linux/bsg.h
@@ -60,8 +60,13 @@ struct bsg_class_device {
extern int bsg_register_queue(struct request_queue *, struct device *, const char *);
extern void bsg_unregister_queue(struct request_queue *);
#else
-#define bsg_register_queue(disk, dev, name) (0)
-#define bsg_unregister_queue(disk) do { } while (0)
+static inline int bsg_register_queue(struct request_queue * rq, struct device *dev, const char *name)
+{
+ return 0;
+}
+static inline void bsg_unregister_queue(struct request_queue *rq)
+{
+}
#endif
#endif /* __KERNEL__ */
parent reply other threads:[~2007-07-23 14:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20070723143637.GB23448@slug>]
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=1185202432.3417.7.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=deweerdt@free.fr \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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