From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: John Garry <john.garry@huawei.com>,
kernel test robot <lkp@intel.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: [mkp-scsi:for-next 93/154] hisi_sas_main.c:undefined reference to `sas_execute_ata_cmd'
Date: Tue, 22 Feb 2022 20:28:50 +0900 [thread overview]
Message-ID: <276308f0-e45e-243a-0058-96c3cf6558f5@opensource.wdc.com> (raw)
In-Reply-To: <59b538b7-b4c5-8111-d2bf-7fb353ecb19b@huawei.com>
On 2/22/22 18:10, John Garry wrote:
> On 22/02/2022 06:52, kernel test robot wrote:
>
> Hi Martin,
>
> Sorry about this. I'm missing a stub function. It is straightforward to fix.
>
> Shall I just resend based on 5.18/scsi-queue?
>
> I'm not sure where that leaves Damien's series.. it just seems easier to
> try to take mine again first as Damien's would need to be rebased again
> (if not based on mine).
May be just send an incremental patch on top of yours+my series ? But I
doubt there will be a conflict anyway.
>
> Thanks,
> John
>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next
>> head: 2988062985d598d6871f47cb8eb70318af5b5b2d
>> commit: 13685dfbad9831580335dc6e2f7a3be14b769686 [93/154] scsi: libsas: Add sas_execute_ata_cmd()
>> config: ia64-buildonly-randconfig-r002-20220221 (https://download.01.org/0day-ci/archive/20220222/202202221427.OvZeGfzt-lkp@intel.com/config)
>> compiler: ia64-linux-gcc (GCC) 11.2.0
>> reproduce (this is a W=1 build):
>> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>> chmod +x ~/bin/make.cross
>> # https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=13685dfbad9831580335dc6e2f7a3be14b769686
>> git remote add mkp-scsi https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git
>> git fetch --no-tags mkp-scsi for-next
>> git checkout 13685dfbad9831580335dc6e2f7a3be14b769686
>> # save the config file to linux build tree
>> mkdir build_dir
>> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=ia64 SHELL=/bin/bash
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>> ia64-linux-ld: drivers/scsi/hisi_sas/hisi_sas_main.o: in function `hisi_sas_softreset_ata_disk':
>>>> hisi_sas_main.c:(.text+0x42f2): undefined reference to `sas_execute_ata_cmd'
>>>> ia64-linux-ld: hisi_sas_main.c:(.text+0x44a2): undefined reference to `sas_execute_ata_cmd'
>> ia64-linux-ld: hisi_sas_main.c:(.text+0x45e2): undefined reference to `sas_execute_ata_cmd'
>> ia64-linux-ld: hisi_sas_main.c:(.text+0x4732): undefined reference to `sas_execute_ata_cmd'
>>
>> ---
>> 0-DAY CI Kernel Test Service, Intel Corporation
>> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>> .
>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-02-22 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 6:52 kernel test robot
2022-02-22 9:10 ` John Garry
2022-02-22 11:28 ` Damien Le Moal [this message]
2022-02-22 11:42 ` John Garry
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=276308f0-e45e-243a-0058-96c3cf6558f5@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=hch@lst.de \
--cc=john.garry@huawei.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--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®