From: kernel test robot <lkp@intel.com>
To: Bikash Hazarika <bhazarika@marvell.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Himanshu Madhani <himanshu.madhani@oracle.com>,
Saurav Kashyap <skashyap@marvell.com>,
Arun Easi <aeasi@marvell.com>,
Nilesh Javali <njavali@marvell.com>
Subject: [linux-next:master 2541/11103] drivers/scsi/qla2xxx/qla_isr.c:3443:32: sparse: sparse: incorrect type in assignment (different base types)
Date: Mon, 15 Feb 2021 07:18:37 +0800 [thread overview]
Message-ID: <202102150733.GEizdvZt-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2473 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 07f7e57c63aaa2afb4ea31edef05e08699a63a00
commit: a04658594399e1fa25f984601b77ee840e6aaf01 [2541/11103] scsi: qla2xxx: Wait for ABTS response on I/O timeouts for NVMe
config: powerpc64-randconfig-s031-20210214 (attached as .config)
compiler: powerpc-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.3-215-g0fb77bb6-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a04658594399e1fa25f984601b77ee840e6aaf01
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout a04658594399e1fa25f984601b77ee840e6aaf01
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=powerpc64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
"sparse warnings: (new ones prefixed by >>)"
>> drivers/scsi/qla2xxx/qla_isr.c:3443:32: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le16 [usertype] comp_status @@ got int @@
drivers/scsi/qla2xxx/qla_isr.c:3443:32: sparse: expected restricted __le16 [usertype] comp_status
drivers/scsi/qla2xxx/qla_isr.c:3443:32: sparse: got int
vim +3443 drivers/scsi/qla2xxx/qla_isr.c
3428
3429 static void
3430 qla24xx_abort_iocb_entry(scsi_qla_host_t *vha, struct req_que *req,
3431 struct abort_entry_24xx *pkt)
3432 {
3433 const char func[] = "ABT_IOCB";
3434 srb_t *sp;
3435 srb_t *orig_sp = NULL;
3436 struct srb_iocb *abt;
3437
3438 sp = qla2x00_get_sp_from_handle(vha, func, req, pkt);
3439 if (!sp)
3440 return;
3441
3442 abt = &sp->u.iocb_cmd;
> 3443 abt->u.abt.comp_status = le16_to_cpu(pkt->comp_status);
3444 orig_sp = sp->cmd_sp;
3445 /* Need to pass original sp */
3446 if (orig_sp)
3447 qla_nvme_abort_process_comp_status(pkt, orig_sp);
3448
3449 sp->done(sp, 0);
3450 }
3451
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 28492 bytes --]
reply other threads:[~2021-02-14 23:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202102150733.GEizdvZt-lkp@intel.com \
--to=lkp@intel.com \
--cc=aeasi@marvell.com \
--cc=bhazarika@marvell.com \
--cc=himanshu.madhani@oracle.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=martin.petersen@oracle.com \
--cc=njavali@marvell.com \
--cc=skashyap@marvell.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