From: kbuild test robot <lkp@intel.com>
To: Charles Chiou <ch1102chiou@gmail.com>
Cc: kbuild-all@01.org, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, linus.chen@tw.promise.com,
grace.chang@tw.promise.com, victor.p@promise.com,
eva.cheng@tw.promise.com, charles.chiou@tw.promise.com,
julian.calaby@gmail.com, Paul <paul.lyu@tw.promise.com>
Subject: Re: [v2 PATCH 1/2] scsi:stex.c Support Pegasus 3 product
Date: Tue, 14 Jun 2016 15:24:56 +0800 [thread overview]
Message-ID: <201606141550.tfSQQjSr%fengguang.wu@intel.com> (raw)
In-Reply-To: <1465885263-8553-1-git-send-email-ch1102chiou@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2926 bytes --]
Hi,
[auto build test WARNING on scsi/for-next]
[also build test WARNING on v4.7-rc3 next-20160609]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Charles-Chiou/scsi-stex-c-Support-Pegasus-3-product/20160614-142621
base: https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-next
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
All warnings (new ones prefixed by >>):
drivers/scsi/stex.c: In function 'stex_handshake':
>> drivers/scsi/stex.c:1208:2: warning: 'scratch' may be used uninitialized in this function [-Wmaybe-uninitialized]
memset(scratch, 0, scratch_size);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/scsi/stex.c:1111:10: note: 'scratch' was declared here
__le32 *scratch;
^~~~~~~
vim +/scratch +1208 drivers/scsi/stex.c
0f3f6ee6 Ed Lin 2009-03-31 1192 msleep(1);
0f3f6ee6 Ed Lin 2009-03-31 1193 }
2a48e931 Charles 2016-06-14 1194 } else {
2a48e931 Charles 2016-06-14 1195 while ((readl(base + MAILBOX_BASE + MAILBOX_HNDSHK_STS)
2a48e931 Charles 2016-06-14 1196 & SS_STS_HANDSHAKE) == 0) {
2a48e931 Charles 2016-06-14 1197 if (time_after(jiffies, before + MU_MAX_DELAY * HZ)) {
2a48e931 Charles 2016-06-14 1198 printk(KERN_ERR DRV_NAME
2a48e931 Charles 2016-06-14 1199 "(%s): no signature after handshake frame\n",
2a48e931 Charles 2016-06-14 1200 pci_name(hba->pdev));
2a48e931 Charles 2016-06-14 1201 ret = -1;
2a48e931 Charles 2016-06-14 1202 break;
2a48e931 Charles 2016-06-14 1203 }
2a48e931 Charles 2016-06-14 1204 rmb();
2a48e931 Charles 2016-06-14 1205 msleep(1);
2a48e931 Charles 2016-06-14 1206 }
2a48e931 Charles 2016-06-14 1207 }
9eb46d2a Ed Lin 2009-09-28 @1208 memset(scratch, 0, scratch_size);
0f3f6ee6 Ed Lin 2009-03-31 1209 msg_h->flag = 0;
2a48e931 Charles 2016-06-14 1210
0f3f6ee6 Ed Lin 2009-03-31 1211 return ret;
0f3f6ee6 Ed Lin 2009-03-31 1212 }
0f3f6ee6 Ed Lin 2009-03-31 1213
0f3f6ee6 Ed Lin 2009-03-31 1214 static int stex_handshake(struct st_hba *hba)
0f3f6ee6 Ed Lin 2009-03-31 1215 {
0f3f6ee6 Ed Lin 2009-03-31 1216 int err;
:::::: The code at line 1208 was first introduced by commit
:::::: 9eb46d2a08de537e14e92216bf18e7cb541d2f67 [SCSI] stex: add support for reset request from firmware
:::::: TO: Ed Lin <ed.lin@promise.com>
:::::: CC: James Bottomley <James.Bottomley@suse.de>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 54771 bytes --]
next prev parent reply other threads:[~2016-06-14 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 6:21 Charles Chiou
2016-06-14 6:49 ` kbuild test robot
2016-06-14 7:24 ` kbuild test robot [this message]
2016-06-14 7:25 ` kbuild test robot
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=201606141550.tfSQQjSr%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ch1102chiou@gmail.com \
--cc=charles.chiou@tw.promise.com \
--cc=eva.cheng@tw.promise.com \
--cc=grace.chang@tw.promise.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=julian.calaby@gmail.com \
--cc=kbuild-all@01.org \
--cc=linus.chen@tw.promise.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=paul.lyu@tw.promise.com \
--cc=victor.p@promise.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®