From: Christoph Hellwig <hch@lst.de>
To: Guixin Liu <kanie@linux.alibaba.com>
Cc: kernel test robot <lkp@intel.com>,
Keith Busch <kbusch@kernel.org>,
oe-kbuild-all@lists.linux.dev, linux-nvme@lists.infradead.org,
Dmitry Bogdanov <d.bogdanov@yadro.com>,
Christoph Hellwig <hch@lst.de>,
Chaitanya Kulkarni <kch@nvidia.com>
Subject: Re: [linux-nvme:nvme-6.13 7/7] drivers/nvme/target/pr.c:857:34: sparse: sparse: incorrect type in assignment (different base types)
Date: Fri, 8 Nov 2024 08:10:43 +0100 [thread overview]
Message-ID: <20241108071043.GA9339@lst.de> (raw)
In-Reply-To: <c44c4ea6-ef4d-4152-ba21-9a76011dd75e@linux.alibaba.com>
On Fri, Nov 08, 2024 at 11:29:35AM +0800, Guixin Liu wrote:
> I miss here should use cpu_to_le16, should I send a v20 to fix this?
>
> Best Regards,
Just send an incremental fix that can be folded in.
prev parent reply other threads:[~2024-11-08 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 3:18 [linux-nvme:nvme-6.13 7/7] drivers/nvme/target/pr.c:857:34: sparse: sparse: incorrect type in assignment (different base types) kernel test robot
2024-11-08 3:29 ` Guixin Liu
2024-11-08 7:10 ` 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=20241108071043.GA9339@lst.de \
--to=hch@lst.de \
--cc=d.bogdanov@yadro.com \
--cc=kanie@linux.alibaba.com \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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