From: kbuild test robot <lkp@intel.com>
To: DingXiang <dingxiang@huawei.com>
Cc: kbuild-all@01.org, tj@kernel.org, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com, fangwei1@huawei.com,
miaoxie@huawei.com, wangyijing@huawei.com,
zhangaihua1@huawei.com, zhaohongjiang@huawei.com,
houtao1@huawei.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, dingxiang@huawei.com
Subject: Re: [PATCH V2] libata:fix kernel panic when hotplug
Date: Thu, 16 Jun 2016 11:29:23 +0800 [thread overview]
Message-ID: <201606161122.5x9AWvQc%fengguang.wu@intel.com> (raw)
In-Reply-To: <1466045756-16425-1-git-send-email-dingxiang@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
Hi,
[auto build test ERROR on tj-libata/for-next]
[also build test ERROR on v4.7-rc3 next-20160615]
[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/DingXiang/libata-fix-kernel-panic-when-hotplug/20160616-105155
base: https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata for-next
config: x86_64-randconfig-s5-06161042 (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
All errors (new ones prefixed by >>):
drivers/ata/libata-eh.c: In function 'ata_scsi_port_error_handler':
>> drivers/ata/libata-eh.c:820:19: error: 'ATA_PFLAG_SAS_HOST' undeclared (first use in this function)
!(ap->pflags & ATA_PFLAG_SAS_HOST))
^~~~~~~~~~~~~~~~~~
drivers/ata/libata-eh.c:820:19: note: each undeclared identifier is reported only once for each function it appears in
vim +/ATA_PFLAG_SAS_HOST +820 drivers/ata/libata-eh.c
814 /* clean up */
815 spin_lock_irqsave(ap->lock, flags);
816
817 if (ap->pflags & ATA_PFLAG_LOADING)
818 ap->pflags &= ~ATA_PFLAG_LOADING;
819 else if ((ap->pflags & ATA_PFLAG_SCSI_HOTPLUG) &&
> 820 !(ap->pflags & ATA_PFLAG_SAS_HOST))
821 schedule_delayed_work(&ap->hotplug_task, 0);
822
823 if (ap->pflags & ATA_PFLAG_RECOVERED)
---
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: 27134 bytes --]
next prev parent reply other threads:[~2016-06-16 3:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 2:55 DingXiang
2016-06-16 3:29 ` kbuild test robot [this message]
2016-06-16 7:16 ` 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=201606161122.5x9AWvQc%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dingxiang@huawei.com \
--cc=fangwei1@huawei.com \
--cc=houtao1@huawei.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=miaoxie@huawei.com \
--cc=tj@kernel.org \
--cc=wangyijing@huawei.com \
--cc=zhangaihua1@huawei.com \
--cc=zhaohongjiang@huawei.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®