linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vikas Chaudhary <vikas.chaudhary@qlogic.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Karen Higgins <karen.higgins@qlogic.com>,
	Ravi Anand <ravi.anand@qlogic.com>,
	James Bottomley <James.Bottomley@suse.de>
Subject: RE: linux-next: build warnings in Linus'  tree
Date: Sat, 7 Aug 2010 01:13:12 -0700	[thread overview]
Message-ID: <5E4F49720D0BAD499EE1F01232234BA87128E7CBE3@AVEXMB1.qlogic.org> (raw)
In-Reply-To: <20100807122116.e6421ea0.sfr@canb.auug.org.au>

>-----Original Message-----
>From: Stephen Rothwell [mailto:sfr@canb.auug.org.au]
>Sent: Saturday, August 07, 2010 7:51 AM
>To: Vikas Chaudhary
>Cc: linux-next@vger.kernel.org; linux-kernel@vger.kernel.org; Karen
>Higgins; Ravi Anand; James Bottomley
>Subject: linux-next: build warnings in Linus' tree
>
>Hi all,
>
>today's linux-next build (x86_64 allmodconfig) of Linus' tree produced
>these warnings:
>
>drivers/scsi/qla4xxx/ql4_nx.c: In function 'qla4_8xxx_get_flash_info':
>drivers/scsi/qla4xxx/ql4_nx.c:1952: warning: 'mid' may be used
>uninitialized in this function
>drivers/scsi/qla4xxx/ql4_nx.c:1952: note: 'mid' was declared here
>drivers/scsi/qla4xxx/ql4_nx.c:1952: warning: 'fid' may be used
>uninitialized in this function
>drivers/scsi/qla4xxx/ql4_nx.c:1952: note: 'fid' was declared here
>
>Introduced by commit f4f5df23bf72208d0c2f1d8be629839924c2f4c2 ("[SCSI]
>qla4xxx: Added support for ISP82XX").  I don't think that these are false
>positives.
>

Yes, Sorry. I am sending patch in next mail on top of latest
scsi-misc-2.6 tree to fix this warning. 

>--
>Cheers,
>Stephen Rothwell                    sfr@canb.auug.org.au
>http://www.canb.auug.org.au/~sfr/

  reply	other threads:[~2010-08-07  8:14 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-07  2:21 linux-next: build warnings in Linus' tree Stephen Rothwell
2010-08-07  8:13 ` Vikas Chaudhary [this message]
2010-08-17  1:24 Stephen Rothwell
2010-08-30  1:42 ` Stephen Rothwell
2010-08-30  6:08   ` Zhang Rui
2010-09-03  2:01     ` Stephen Rothwell
2010-09-03  2:36     ` Len Brown
2010-09-17  4:26     ` Stephen Rothwell
2010-09-27 13:31       ` Stephen Rothwell
2011-01-14  0:09 Stephen Rothwell
2011-01-14  0:17 ` Andrew Morton
2011-01-14  1:06   ` Greg KH
2011-01-14  0:17 Stephen Rothwell
2011-05-23  1:25 Stephen Rothwell
2011-05-23  2:31 ` Eduardo Silva
2011-08-15  1:57 Stephen Rothwell
2013-07-04  4:58 Stephen Rothwell
2013-07-09 21:48 ` Nikolova, Tatyana E
2017-11-13 21:52 Stephen Rothwell
2017-11-13 22:03 ` Linus Torvalds
2020-04-03 22:19 Stephen Rothwell
2020-04-03 23:16 ` Rob Herring
2020-04-03 23:31   ` Nicolas Saenz Julienne
2020-09-07 23:11 Stephen Rothwell
2020-09-08 13:14 ` Josh Poimboeuf
2020-09-09  0:15   ` Stephen Rothwell
2021-10-08  5:47 Stephen Rothwell
2021-10-10 21:27 ` Stephen Rothwell
2021-10-11 20:42   ` Rob Herring
2021-10-12 14:39     ` Arnd Bergmann
2021-10-13 22:12       ` Anatolij Gustschin
2021-10-13 22:17         ` Rob Herring
2021-10-13 22:28           ` Anatolij Gustschin
2021-10-13 23:22             ` Rob Herring
2021-10-14  8:44         ` Arnd Bergmann
2021-10-14 12:24           ` Anatolij Gustschin
2021-10-12 10:56 Stephen Rothwell
2021-10-12 20:13 ` Randy Dunlap
2021-11-05  5:03 Stephen Rothwell
2021-11-22 22:44 Stephen Rothwell
2021-11-23  7:04 ` Borislav Petkov
2022-01-27  4:24 Stephen Rothwell
2022-01-27  4:30 Stephen Rothwell
2022-01-27  6:01 ` Christoph Hellwig
2022-01-27 16:44   ` Stephen Rothwell
2022-05-26  7:21 Stephen Rothwell
2022-06-14  6:57 Stephen Rothwell

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=5E4F49720D0BAD499EE1F01232234BA87128E7CBE3@AVEXMB1.qlogic.org \
    --to=vikas.chaudhary@qlogic.com \
    --cc=James.Bottomley@suse.de \
    --cc=karen.higgins@qlogic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ravi.anand@qlogic.com \
    --cc=sfr@canb.auug.org.au \
    /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).