From: Keith Busch <kbusch@kernel.org>
To: Maurizio Lombardi <mlombard@redhat.com>
Cc: sagi@grimberg.me, hare@suse.de, dwagner@suse.de,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 0/2] nvmet-auth: fix some minor bugs
Date: Tue, 16 Apr 2024 10:44:14 -0600 [thread overview]
Message-ID: <Zh6q3mtbt4a7H4sW@kbusch-mbp> (raw)
In-Reply-To: <20240410094842.370170-1-mlombard@redhat.com>
On Wed, Apr 10, 2024 at 11:48:40AM +0200, Maurizio Lombardi wrote:
> First patch modifies nvmet_auth_host_hash() so it correctly returns
> the error code to its caller.
>
> The second patch replaces a pr_debug() with pr_err().
Thanks, applied to nvme-6.9.
prev parent reply other threads:[~2024-04-16 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 9:48 [PATCH 0/2] nvmet-auth: fix some minor bugs Maurizio Lombardi
2024-04-10 9:48 ` [PATCH 1/2] nvmet-auth: return the error code to the nvmet_auth_host_hash() callers Maurizio Lombardi
2024-04-10 13:57 ` Sagi Grimberg
2024-04-16 2:51 ` Chaitanya Kulkarni
2024-04-10 9:48 ` [PATCH 2/2] nvmet-auth: replace pr_debug() with pr_err() to report an error Maurizio Lombardi
2024-04-10 13:57 ` Sagi Grimberg
2024-04-16 2:51 ` Chaitanya Kulkarni
2024-04-16 16:44 ` Keith Busch [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=Zh6q3mtbt4a7H4sW@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=linux-nvme@lists.infradead.org \
--cc=mlombard@redhat.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;
as well as URLs for NNTP newsgroup(s).