From: Christoph Hellwig <hch@lst.de>
To: kernel test robot <lkp@intel.com>
Cc: Sagi Grimberg <sagi@grimberg.me>,
kbuild-all@lists.01.org, linux-nvme@lists.infradead.org,
Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>
Subject: Re: [linux-nvme:nvme-5.17 1/2] drivers/nvme/host/tcp.c:920:25: sparse: sparse: incorrect type in argument 2 (different base types)
Date: Wed, 9 Feb 2022 14:51:27 +0100 [thread overview]
Message-ID: <20220209135127.GA20537@lst.de> (raw)
In-Reply-To: <202202092122.25VLa0rQ-lkp@intel.com>
I've folded this fix in:
diff --git a/drivers/nvme/host/tcp.c b/drivers/nvme/host/tcp.c
index 1096a0b0a268f..891a36d02e7c7 100644
--- a/drivers/nvme/host/tcp.c
+++ b/drivers/nvme/host/tcp.c
@@ -917,7 +917,7 @@ static void nvme_tcp_fail_request(struct nvme_tcp_request *req)
union nvme_result res = {};
nvme_complete_async_event(&req->queue->ctrl->ctrl,
- NVME_SC_HOST_PATH_ERROR, &res);
+ cpu_to_le16(NVME_SC_HOST_PATH_ERROR), &res);
} else {
nvme_tcp_end_request(blk_mq_rq_from_pdu(req),
NVME_SC_HOST_PATH_ERROR);
prev parent reply other threads:[~2022-02-09 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 13:37 [linux-nvme:nvme-5.17 1/2] drivers/nvme/host/tcp.c:920:25: sparse: sparse: incorrect type in argument 2 (different base types) kernel test robot
2022-02-09 13:51 ` Christoph Hellwig [this message]
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=20220209135127.GA20537@lst.de \
--to=hch@lst.de \
--cc=hare@suse.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lkp@intel.com \
--cc=sagi@grimberg.me \
/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