From: kbuild test robot <lkp@intel.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: kbuild-all@01.org, James Bottomley <jejb@linux.vnet.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Hannes Reinecke <hare@suse.de>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Linux SCSI Mailinglist <linux-scsi@vger.kernel.org>,
Johannes Thumshirn <jthumshirn@suse.de>
Subject: Re: [PATCH v3 1/3] sas: provide stub implementation for scsi_is_sas_rphy
Date: Wed, 17 Aug 2016 17:56:47 +0800 [thread overview]
Message-ID: <201608171706.iwWe0sTm%fengguang.wu@intel.com> (raw)
In-Reply-To: <9ff63d3df2286ad79b32bea6be0b3fb94cf67a53.1471423022.git.jthumshirn@suse.de>
[-- Attachment #1: Type: text/plain, Size: 3605 bytes --]
Hi Johannes,
[auto build test WARNING on scsi/for-next]
[also build test WARNING on v4.8-rc2 next-20160817]
[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/Johannes-Thumshirn/Fix-panic-when-a-SES-device-is-attached-to-a-hpsa-logical-volume/20160817-165528
base: https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-next
config: i386-randconfig-x009-201633 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
In file included from include/linux/init.h:4:0,
from drivers/scsi/scsi_transport_sas.c:26:
drivers/scsi/scsi_transport_sas.c: In function 'do_sas_phy_delete':
drivers/scsi/scsi_transport_sas.c:338:24: error: implicit declaration of function 'scsi_is_sas_phy' [-Werror=implicit-function-declaration]
else if (pass == 1 && scsi_is_sas_phy(dev))
^
include/linux/compiler.h:149:30: note: in definition of macro '__trace_if'
if (__builtin_constant_p(!!(cond)) ? !!(cond) : \
^~~~
>> drivers/scsi/scsi_transport_sas.c:338:7: note: in expansion of macro 'if'
else if (pass == 1 && scsi_is_sas_phy(dev))
^~
cc1: some warnings being treated as errors
vim +/if +338 drivers/scsi/scsi_transport_sas.c
c7ebbbce Christoph Hellwig 2005-09-09 322 if (!shost->transportt)
c7ebbbce Christoph Hellwig 2005-09-09 323 return 0;
c7ebbbce Christoph Hellwig 2005-09-09 324 if (shost->transportt->host_attrs.ac.class !=
c7ebbbce Christoph Hellwig 2005-09-09 325 &sas_host_class.class)
c7ebbbce Christoph Hellwig 2005-09-09 326 return 0;
c7ebbbce Christoph Hellwig 2005-09-09 327
c7ebbbce Christoph Hellwig 2005-09-09 328 i = to_sas_internal(shost->transportt);
c7ebbbce Christoph Hellwig 2005-09-09 329 return &i->t.host_attrs.ac == cont;
c7ebbbce Christoph Hellwig 2005-09-09 330 }
c7ebbbce Christoph Hellwig 2005-09-09 331
c7ebbbce Christoph Hellwig 2005-09-09 332 static int do_sas_phy_delete(struct device *dev, void *data)
c7ebbbce Christoph Hellwig 2005-09-09 333 {
65c92b09 James Bottomley 2006-06-28 334 int pass = (int)(unsigned long)data;
65c92b09 James Bottomley 2006-06-28 335
65c92b09 James Bottomley 2006-06-28 336 if (pass == 0 && scsi_is_sas_port(dev))
65c92b09 James Bottomley 2006-06-28 337 sas_port_delete(dev_to_sas_port(dev));
65c92b09 James Bottomley 2006-06-28 @338 else if (pass == 1 && scsi_is_sas_phy(dev))
c7ebbbce Christoph Hellwig 2005-09-09 339 sas_phy_delete(dev_to_phy(dev));
c7ebbbce Christoph Hellwig 2005-09-09 340 return 0;
c7ebbbce Christoph Hellwig 2005-09-09 341 }
c7ebbbce Christoph Hellwig 2005-09-09 342
c7ebbbce Christoph Hellwig 2005-09-09 343 /**
3b91d09c James Bottomley 2015-12-09 344 * is_sas_attached - check if device is SAS attached
3b91d09c James Bottomley 2015-12-09 345 * @sdev: scsi device to check
3b91d09c James Bottomley 2015-12-09 346 *
:::::: The code at line 338 was first introduced by commit
:::::: 65c92b09acf0218b64f1c7ba4fdabeb8b732c876 [SCSI] scsi_transport_sas: introduce a sas_port entity
:::::: TO: James Bottomley <James.Bottomley@steeleye.com>
:::::: CC: James Bottomley <jejb@mulgrave.il.steeleye.com>
---
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: 27190 bytes --]
next prev parent reply other threads:[~2016-08-17 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 8:40 [PATCH v3 0/3] Fix panic when a SES device is attached to a hpsa logical volume Johannes Thumshirn
2016-08-17 8:40 ` [PATCH v3 1/3] sas: provide stub implementation for scsi_is_sas_rphy Johannes Thumshirn
2016-08-17 9:19 ` kbuild test robot
2016-08-17 9:56 ` kbuild test robot [this message]
2016-08-17 8:40 ` [PATCH v3 2/3] ses: use scsi_is_sas_rphy instead of is_sas_attached Johannes Thumshirn
2016-08-17 8:40 ` [PATCH v3 3/3] sas: remove is_sas_attached() Johannes Thumshirn
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=201608171706.iwWe0sTm%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=hare@suse.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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
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®