From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-scsi@vger.kernel.org, James.Bottomley@suse.de
Subject: Re: [PATCH]: aic94xx: fix uninitialized variable warning
Date: Fri, 28 May 2010 21:18:07 +0200 [thread overview]
Message-ID: <201005282118.08243.eike-kernel@sf-tec.de> (raw)
In-Reply-To: <20100527182056.24051.65113.sendpatchset@prarit.bos.redhat.com>
[-- Attachment #1: Type: Text/Plain, Size: 1064 bytes --]
Prarit Bhargava wrote:
> Fixes warning:
>
> drivers/scsi/aic94xx/aic94xx_sds.c: In function
> âasd_process_ctrl_a_userâ: drivers/scsi/aic94xx/aic94xx_sds.c:985:
> error: âoffsâ may be used uninitialized in this function
Your mailer has messed this up as it did not declare any character set. This
was probably UTF8 or something like that.
> diff --git a/drivers/scsi/aic94xx/aic94xx_sds.c
> b/drivers/scsi/aic94xx/aic94xx_sds.c index edb43fd..2f1751a 100644
> --- a/drivers/scsi/aic94xx/aic94xx_sds.c
> +++ b/drivers/scsi/aic94xx/aic94xx_sds.c
> @@ -982,7 +982,7 @@ static int asd_process_ctrl_a_user(struct asd_ha_struct
> *asd_ha, struct asd_flash_dir *flash_dir)
> {
> int err, i;
> - u32 offs, size;
> + u32 uninitialized_var(offs), size;
> struct asd_ll_el *el;
> struct asd_ctrla_phy_settings *ps;
> struct asd_ctrla_phy_settings dflt_ps;
I would vote for putting the declarations if different lines if one of them
gets initialized or otherwise treated specially as it is otherwise hardly
readable.
Eike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-05-28 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 18:24 [PATCH]: aic94xx: fix uninitialized variable warning Prarit Bhargava
2010-05-28 19:18 ` Rolf Eike Beer [this message]
2010-06-07 18:52 ` Prarit Bhargava
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=201005282118.08243.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=James.Bottomley@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=prarit@redhat.com \
/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.