Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Hannes Reinecke <hare@suse.de>
Subject: linux-next: build warnings after merge of the scsi-mkp tree
Date: Tue, 13 Feb 2018 14:00:24 +1100
Message-ID: <20180213140024.0fb09872@canb.auug.org.au> (raw)

Hi Martin,

After merging the scsi-mkp tree, today's linux-next build (x86_64
allmodconfig) produced these warnings:

drivers/scsi/myrb.c: In function 'myrb_get_ldev_info':
drivers/scsi/myrb.c:428:10: warning: 'ldev_num' may be used uninitialized in this function [-Wmaybe-uninitialized]
   sdev = scsi_device_lookup(shost, myrb_logical_channel(shost),
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        ldev_num, 0);
        ~~~~~~~~~~~~
drivers/scsi/myrs.c: In function 'myrs_handle_scsi':
drivers/scsi/myrs.c:2175:6: warning: 'status' may be used uninitialized in this function [-Wmaybe-uninitialized]
   if (status == DAC960_V2_AbnormalCompletion &&
      ^
drivers/scsi/myrs.c: In function 'myrs_log_event':
drivers/scsi/myrs.c:988:21: warning: 'cmd_specific' may be used uninitialized in this function [-Wmaybe-uninitialized]
         cmd_specific[0], cmd_specific[1],
                     ^
drivers/scsi/myrs.c:986:19: warning: 'sense_info' may be used uninitialized in this function [-Wmaybe-uninitialized]
         sense_info[0], sense_info[1],
                   ^

Introduced by commits

  dd47c1072226 ("scsi: myrb: Add Mylex RAID controller (block interface)")
  8a8606895947 ("scsi: myrs: Add Mylex RAID controller (SCSI interface)")

-- 
Cheers,
Stephen Rothwell

             reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13  3:00 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-03  6:03 Stephen Rothwell
2021-04-21  6:03 ` Stephen Rothwell
2017-06-28  5:55 Stephen Rothwell
2017-06-29  5:07 ` Stephen Rothwell
2017-06-29 18:35   ` Madhani, Himanshu

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=20180213140024.0fb09872@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=hare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=martin.petersen@oracle.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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git