From: Sagi Grimberg <sagi@grimberg.me>
To: Maurizio Lombardi <mlombard@redhat.com>, kbusch@kernel.org
Cc: hare@suse.de, dwagner@suse.de, linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvmet-auth: return the error code to the nvmet_auth_ctrl_hash() callers
Date: Sun, 14 Apr 2024 11:35:10 +0300 [thread overview]
Message-ID: <f4717e6c-1082-42ab-aeab-e6f2b559dd31@grimberg.me> (raw)
In-Reply-To: <20240412134154.565298-1-mlombard@redhat.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
next prev parent reply other threads:[~2024-04-14 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 13:41 [PATCH] nvmet-auth: return the error code to the nvmet_auth_ctrl_hash() callers Maurizio Lombardi
2024-04-14 8:35 ` Sagi Grimberg [this message]
2024-04-16 2:38 ` Chaitanya Kulkarni
2024-05-07 15:02 ` Keith Busch
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=f4717e6c-1082-42ab-aeab-e6f2b559dd31@grimberg.me \
--to=sagi@grimberg.me \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mlombard@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox