From: James Bottomley <James.Bottomley@suse.de>
To: Matthew Wilcox <matthew@wil.cx>
Cc: "Justin P. Mattock" <justinmattock@gmail.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 5/5 v2]scsi:hosts.c Fix warning: variable 'rval' set but not used
Date: Sat, 19 Jun 2010 14:32:51 -0500 [thread overview]
Message-ID: <1276975971.4416.19.camel@mulgrave.site> (raw)
In-Reply-To: <20100618204730.GL9298@parisc-linux.org>
On Fri, 2010-06-18 at 14:47 -0600, Matthew Wilcox wrote:
> On Fri, Jun 18, 2010 at 01:16:07PM -0700, Justin P. Mattock wrote:
> > @@ -420,7 +419,8 @@ 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);
> > + printk(KERN_WARNING "scsi%d: error handler thread failed to spawn, error = %ld\n",
> > + shost->host_no, PTR_ERR(shost->ehandler));
>
> Surely this should simply be:
>
> shost_printk(KERN_WARNING, shost, "error handler thread failed"
> "to spawn (%ld)\n", PTR_ERR(shost->ehandler));
Actually, I'm wary of doing this: the device isn't fully initialised
(it's unparented and not added to the system) so that could cause
problems down the road for intelligent error gathering. It's why we
tend to do the printk scsi%d (or dev_printk on the parent) thing up
until scsi_host_add().
James
prev parent reply other threads:[~2010-06-19 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 20:16 [PATCH 5/5 v2]scsi:hosts.c Fix warning: variable 'rval' set but not used Justin P. Mattock
2010-06-18 20:28 ` James Bottomley
2010-06-18 20:38 ` Justin P. Mattock
2010-06-18 20:47 ` Matthew Wilcox
2010-06-18 21:24 ` Justin P. Mattock
2010-06-19 19:32 ` James Bottomley [this message]
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=1276975971.4416.19.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=justinmattock@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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