All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michael.christie@oracle.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Manish Rangankar <mrangankar@marvell.com>
Subject: Re: [linux-next:master 6351/6976] drivers/scsi/qedi/qedi_fw.c:1039:45: sparse: sparse: incorrect type in assignment (different base types)
Date: Thu, 3 Jun 2021 15:18:56 -0500	[thread overview]
Message-ID: <bf36dba3-ba42-55ff-abf3-4f86607a1084@oracle.com> (raw)
In-Reply-To: <202106040154.rvggrEBO-lkp@intel.com>

On 6/3/21 12:10 PM, kernel test robot wrote:
> tree:   https://urldefense.com/v3/__https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git__;!!GqivPVa7Brio!L-QQ6Mx-OZszOnFdN5lLFW-jo2vsB4dfH_ouv1FJdtmad2ZuSk4O5BrtZy-la7gW8-n1$  master
> head:   3ebdbe7aa5dd825d609c3433c35c13b440a61c52
> commit: ed1b86ba0fba3d586cd53057551a95197b0a37ad [6351/6976] scsi: qedi: Wake up if cmd_cleanup_req is set

I don't think this patch caused the issue being reported. It only touched
qedi_process_cmd_cleanup_resp but the new warning is in qedi_send_iscsi_login. Tt
also didn't add any new warnings in qedi_process_cmd_cleanup_resp:

>    drivers/scsi/qedi/qedi_fw.c:741:28: sparse: sparse: incorrect type in initializer (different base types) @@     expected unsigned int [usertype] proto_itt @@     got restricted __le16 [usertype] itid @@
>    drivers/scsi/qedi/qedi_fw.c:741:28: sparse:     expected unsigned int [usertype] proto_itt
>    drivers/scsi/qedi/qedi_fw.c:741:28: sparse:     got restricted __le16 [usertype] itid
>    drivers/scsi/qedi/qedi_fw.c:751:19: sparse: sparse: incorrect type in assignment (different base types) @@     expected unsigned int [usertype] iscsi_cid @@     got restricted __le16 [usertype] conn_id @@
>    drivers/scsi/qedi/qedi_fw.c:751:19: sparse:     expected unsigned int [usertype] iscsi_cid
>    drivers/scsi/qedi/qedi_fw.c:751:19: sparse:     got restricted __le16 [usertype] conn_id
>    drivers/scsi/qedi/qedi_fw.c:802:9: sparse: sparse: cast to restricted itt_t


WARNING: multiple messages have this Message-ID (diff)
From: Mike Christie <michael.christie@oracle.com>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 6351/6976] drivers/scsi/qedi/qedi_fw.c:1039:45: sparse: sparse: incorrect type in assignment (different base types)
Date: Thu, 03 Jun 2021 15:18:56 -0500	[thread overview]
Message-ID: <bf36dba3-ba42-55ff-abf3-4f86607a1084@oracle.com> (raw)
In-Reply-To: <202106040154.rvggrEBO-lkp@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1521 bytes --]

On 6/3/21 12:10 PM, kernel test robot wrote:
> tree:   https://urldefense.com/v3/__https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git__;!!GqivPVa7Brio!L-QQ6Mx-OZszOnFdN5lLFW-jo2vsB4dfH_ouv1FJdtmad2ZuSk4O5BrtZy-la7gW8-n1$  master
> head:   3ebdbe7aa5dd825d609c3433c35c13b440a61c52
> commit: ed1b86ba0fba3d586cd53057551a95197b0a37ad [6351/6976] scsi: qedi: Wake up if cmd_cleanup_req is set

I don't think this patch caused the issue being reported. It only touched
qedi_process_cmd_cleanup_resp but the new warning is in qedi_send_iscsi_login. Tt
also didn't add any new warnings in qedi_process_cmd_cleanup_resp:

>    drivers/scsi/qedi/qedi_fw.c:741:28: sparse: sparse: incorrect type in initializer (different base types) @@     expected unsigned int [usertype] proto_itt @@     got restricted __le16 [usertype] itid @@
>    drivers/scsi/qedi/qedi_fw.c:741:28: sparse:     expected unsigned int [usertype] proto_itt
>    drivers/scsi/qedi/qedi_fw.c:741:28: sparse:     got restricted __le16 [usertype] itid
>    drivers/scsi/qedi/qedi_fw.c:751:19: sparse: sparse: incorrect type in assignment (different base types) @@     expected unsigned int [usertype] iscsi_cid @@     got restricted __le16 [usertype] conn_id @@
>    drivers/scsi/qedi/qedi_fw.c:751:19: sparse:     expected unsigned int [usertype] iscsi_cid
>    drivers/scsi/qedi/qedi_fw.c:751:19: sparse:     got restricted __le16 [usertype] conn_id
>    drivers/scsi/qedi/qedi_fw.c:802:9: sparse: sparse: cast to restricted itt_t

  reply	other threads:[~2021-06-03 23:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 17:10 [linux-next:master 6351/6976] drivers/scsi/qedi/qedi_fw.c:1039:45: sparse: sparse: incorrect type in assignment (different base types) kernel test robot
2021-06-03 17:10 ` kernel test robot
2021-06-03 20:18 ` Mike Christie [this message]
2021-06-03 20:18   ` Mike Christie
2021-06-07  9:49   ` [kbuild-all] " Rong Chen
2021-06-07  9:49     ` Rong Chen

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=bf36dba3-ba42-55ff-abf3-4f86607a1084@oracle.com \
    --to=michael.christie@oracle.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=martin.petersen@oracle.com \
    --cc=mrangankar@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 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.