From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Keith Busch <kbusch@meta.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"hch@lst.de" <hch@lst.de>
Cc: "sagi@grimberg.me" <sagi@grimberg.me>,
Keith Busch <kbusch@kernel.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] nvme: fix sparse warning on effects masking
Date: Fri, 24 Feb 2023 23:52:02 +0000 [thread overview]
Message-ID: <17b230f3-fb84-d389-250f-9acd54507c00@nvidia.com> (raw)
In-Reply-To: <20230224153424.734731-1-kbusch@meta.com>
On 2/24/2023 7:34 AM, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> The log entries are stored in le32, so use appropriate byte swapping
> macros.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Link: https://lore.kernel.org/oe-kbuild-all/202302242222.PevBhzvC-lkp@intel.com/
> Signed-off-by: Keith Busch <kbusch@kernel.org>
> ---
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2023-02-24 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 15:34 [PATCH] nvme: fix sparse warning on effects masking Keith Busch
2023-02-24 23:52 ` Chaitanya Kulkarni [this message]
2023-02-27 14:06 ` Christoph Hellwig
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=17b230f3-fb84-d389-250f-9acd54507c00@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--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