From: kbuild test robot <lkp@intel.com>
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>,
stable@vger.kernel.org, #@suse.de, v4.5+@suse.de
Subject: Re: [PATCH 1/2] ses: use scsi_is_sas_rphy instead of is_sas_attached
Date: Mon, 15 Aug 2016 22:11:20 +0800 [thread overview]
Message-ID: <201608152258.TcR75AwO%fengguang.wu@intel.com> (raw)
In-Reply-To: <ac01dba641b71f6e61764422ba4a3fa38d636d14.1471251131.git.jthumshirn@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]
Hi Johannes,
[auto build test ERROR on scsi/for-next]
[also build test ERROR on v4.8-rc2 next-20160815]
[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/ses-use-scsi_is_sas_rphy-instead-of-is_sas_attached/20160815-165716
base: https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-next
config: s390-zfcpdump_defconfig (attached as .config)
compiler: s390x-linux-gnu-gcc (Debian 5.4.0-6) 5.4.0 20160609
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=s390
All errors (new ones prefixed by >>):
drivers/built-in.o: In function `ses_match_to_enclosure':
>> drivers/scsi/ses.c:590: undefined reference to `scsi_is_sas_rphy'
>> drivers/scsi/ses.c:591: undefined reference to `sas_get_address'
vim +590 drivers/scsi/ses.c
584 struct efd efd = {
585 .addr = 0,
586 };
587
588 ses_enclosure_data_process(edev, to_scsi_device(edev->edev.parent), 0);
589
> 590 if (scsi_is_sas_rphy(&sdev->sdev_gendev))
> 591 efd.addr = sas_get_address(sdev);
592
593 if (efd.addr) {
594 efd.dev = &sdev->sdev_gendev;
---
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: 6975 bytes --]
WARNING: multiple messages have this Message-ID (diff)
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>,
stable@vger.kernel.org, #@suse.de, v4.5+@suse.de
Subject: Re: [PATCH 1/2] ses: use scsi_is_sas_rphy instead of is_sas_attached
Date: Mon, 15 Aug 2016 22:11:20 +0800 [thread overview]
Message-ID: <201608152258.TcR75AwO%fengguang.wu@intel.com> (raw)
In-Reply-To: <ac01dba641b71f6e61764422ba4a3fa38d636d14.1471251131.git.jthumshirn@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]
Hi Johannes,
[auto build test ERROR on scsi/for-next]
[also build test ERROR on v4.8-rc2 next-20160815]
[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/ses-use-scsi_is_sas_rphy-instead-of-is_sas_attached/20160815-165716
base: https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-next
config: s390-zfcpdump_defconfig (attached as .config)
compiler: s390x-linux-gnu-gcc (Debian 5.4.0-6) 5.4.0 20160609
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=s390
All errors (new ones prefixed by >>):
drivers/built-in.o: In function `ses_match_to_enclosure':
>> drivers/scsi/ses.c:590: undefined reference to `scsi_is_sas_rphy'
>> drivers/scsi/ses.c:591: undefined reference to `sas_get_address'
vim +590 drivers/scsi/ses.c
584 struct efd efd = {
585 .addr = 0,
586 };
587
588 ses_enclosure_data_process(edev, to_scsi_device(edev->edev.parent), 0);
589
> 590 if (scsi_is_sas_rphy(&sdev->sdev_gendev))
> 591 efd.addr = sas_get_address(sdev);
592
593 if (efd.addr) {
594 efd.dev = &sdev->sdev_gendev;
---
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: 6975 bytes --]
next prev parent reply other threads:[~2016-08-15 14:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 8:52 [PATCH 1/2] ses: use scsi_is_sas_rphy instead of is_sas_attached Johannes Thumshirn
2016-08-15 8:52 ` [PATCH 2/2] sas: remove is_sas_attached() Johannes Thumshirn
2016-08-15 14:11 ` kbuild test robot [this message]
2016-08-15 14:11 ` [PATCH 1/2] ses: use scsi_is_sas_rphy instead of is_sas_attached kbuild test robot
2016-08-15 14:25 ` James Bottomley
2016-08-15 14:40 ` Johannes Thumshirn
2016-08-15 14:40 ` Johannes Thumshirn
2016-08-15 14:59 ` James Bottomley
2016-08-15 15:04 ` Johannes Thumshirn
2016-08-15 15:04 ` 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=201608152258.TcR75AwO%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=#@suse.de \
--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 \
--cc=stable@vger.kernel.org \
--cc=v4.5+@suse.de \
/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.