From: Chaitanya Kulkarni <kch@nvidia.com>
To: <hare@suse.de>
Cc: <linux-nvme@lists.infradead.org>, <hch@lst.de>,
<sagi@grimberg.me>, Chaitanya Kulkarni <kch@nvidia.com>
Subject: [PATCH 0/2] nvmet: type missmatch fixes for nvmet-auth
Date: Mon, 18 Jul 2022 16:12:31 -0700 [thread overview]
Message-ID: <20220718231233.3886-1-kch@nvidia.com> (raw)
Hi,
Couple of type mismatch fixes for nvmet-auth reported by
Dan Carpenter.
-ck
Chaitanya Kulkarni (2):
nvmet: fix return value check in auth send
nvmet: fix return value check in auth receive
drivers/nvme/target/fabrics-cmd-auth.c | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
--
2.29.0
next reply other threads:[~2022-07-18 23:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 23:12 Chaitanya Kulkarni [this message]
2022-07-18 23:12 ` [PATCH 1/2] nvmet: fix return value check in auth send Chaitanya Kulkarni
2022-07-19 6:51 ` Hannes Reinecke
2022-07-21 5:41 ` Christoph Hellwig
2022-07-18 23:12 ` [PATCH 2/2] nvmet: fix return value check in auth receive Chaitanya Kulkarni
2022-07-19 6:51 ` Hannes Reinecke
2022-07-21 22:15 ` [PATCH 0/2] nvmet: type missmatch fixes for nvmet-auth Sagi Grimberg
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=20220718231233.3886-1-kch@nvidia.com \
--to=kch@nvidia.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--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