From: "Justin P. Mattock" <justinmattock@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-wireless@vger.kernel.org, linux-pci@vger.kernel.org,
linux-scsi@vger.kernel.org,
"Justin P. Mattock" <justinmattock@gmail.com>
Subject: [PATCH 5/5]scsi:hosts.c Fix warning: variable 'rval' set but not used
Date: Tue, 15 Jun 2010 22:33:54 -0700 [thread overview]
Message-ID: <1276666434-11227-6-git-send-email-justinmattock@gmail.com> (raw)
In-Reply-To: <1276666434-11227-1-git-send-email-justinmattock@gmail.com>
The below patch fixes a warning message generated by gcc 4.6.0
CC drivers/scsi/hosts.o
drivers/scsi/hosts.c: In function 'scsi_host_alloc':
drivers/scsi/hosts.c:328:6: warning: variable 'rval' set but not used
Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
---
drivers/scsi/hosts.c | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/hosts.c b/drivers/scsi/hosts.c
index 6660fa9..00fd6a4 100644
--- a/drivers/scsi/hosts.c
+++ b/drivers/scsi/hosts.c
@@ -325,7 +325,6 @@ struct Scsi_Host *scsi_host_alloc(struct scsi_host_template *sht, int privsize)
{
struct Scsi_Host *shost;
gfp_t gfp_mask = GFP_KERNEL;
- int rval;
if (sht->unchecked_isa_dma && privsize)
gfp_mask |= __GFP_DMA;
@@ -420,7 +419,6 @@ struct Scsi_Host *scsi_host_alloc(struct scsi_host_template *sht, int privsize)
shost->ehandler = kthread_run(scsi_error_handler, shost,
"scsi_eh_%d", shost->host_no);
if (IS_ERR(shost->ehandler)) {
- rval = PTR_ERR(shost->ehandler);
goto fail_kfree;
}
--
1.7.1.rc1.21.gf3bd6
next prev parent reply other threads:[~2010-06-16 5:33 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 5:33 [PATCH 0/5] Fix set but unused variable warnings Justin P. Mattock
2010-06-16 5:33 ` [PATCH 1/5]wireless:hostap_main.c warning: variable 'iface' set but not used Justin P. Mattock
2010-06-16 5:33 ` [PATCH 2/5]wireless:hostap_ap.c Fix warning: variable 'fc' " Justin P. Mattock
2010-06-16 5:33 ` [PATCH 3/5]pci:bus.c Fix variable 'retval' " Justin P. Mattock
2010-06-16 5:42 ` Julian Calaby
2010-06-16 6:56 ` Justin P. Mattock
2010-06-16 6:07 ` Junchang Wang
2010-06-16 6:58 ` Justin P. Mattock
2010-06-16 17:01 ` Justin P. Mattock
2010-06-17 17:15 ` Justin P. Mattock
2010-06-16 5:33 ` [PATCH 4/5]pci:setup_bus.c Fix warning: " Justin P. Mattock
2010-06-18 17:23 ` Jesse Barnes
2010-06-18 17:31 ` Justin P. Mattock
2010-06-18 18:38 ` Justin P. Mattock
2010-06-18 18:48 ` Yinghai Lu
2010-06-18 19:49 ` Jesse Barnes
2010-06-18 19:59 ` Justin P. Mattock
2010-06-18 20:05 ` Jesse Barnes
2010-06-18 20:26 ` Justin P. Mattock
2010-06-18 20:46 ` Jesse Barnes
2010-06-18 21:12 ` Justin P. Mattock
2010-06-16 5:33 ` Justin P. Mattock [this message]
2010-06-16 15:34 ` [PATCH 5/5]scsi:hosts.c Fix warning: variable 'rval' " James Bottomley
2010-06-16 16:00 ` Justin P. Mattock
2010-06-16 17:25 ` Rolf Eike Beer
2010-06-16 17:33 ` James Bottomley
2010-06-16 18:14 ` Justin P. Mattock
2010-06-17 16:16 ` Justin P. Mattock
2010-06-18 19:37 ` James Bottomley
2010-06-18 19:55 ` Justin P. Mattock
2010-06-18 20:17 ` Justin P. Mattock
2010-06-16 5:52 ` [PATCH 0/5] Fix set but unused variable warnings Julian Calaby
2010-06-16 7:01 ` Justin P. Mattock
2010-06-16 11:09 ` Matthew Wilcox
2010-06-16 11:30 ` Julian Calaby
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=1276666434-11227-6-git-send-email-justinmattock@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-wireless@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).