public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: hare@kernel.org
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org, Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH] nvme-fabrics: typo in nvmf_parse_key()
Date: Wed, 21 Feb 2024 11:08:36 -0700	[thread overview]
Message-ID: <ZdY8JAl921AnBWqi@kbusch-mbp> (raw)
In-Reply-To: <20240221134530.142842-1-hare@kernel.org>

On Wed, Feb 21, 2024 at 02:45:30PM +0100, hare@kernel.org wrote:
> From: Hannes Reinecke <hare@suse.de>
> 
> Of course we should use the key if there is no error ...

Fortunately the part that mattered handles the error correctly, but
printing the wrong message is confusing.

Applied to nvme-6.8, thanks!
 
> Signed-off-by: Hannes Reinecke <hare@suse.de>
> ---
>  drivers/nvme/host/fabrics.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/nvme/host/fabrics.c b/drivers/nvme/host/fabrics.c
> index 3499acbf6a82..ab5ac219b70a 100644
> --- a/drivers/nvme/host/fabrics.c
> +++ b/drivers/nvme/host/fabrics.c
> @@ -637,7 +637,7 @@ static struct key *nvmf_parse_key(int key_id)
>  	}
>  
>  	key = key_lookup(key_id);
> -	if (!IS_ERR(key))
> +	if (IS_ERR(key))
>  		pr_err("key id %08x not found\n", key_id);
>  	else
>  		pr_debug("Using key id %08x\n", key_id);
> -- 
> 2.35.3
> 


      parent reply	other threads:[~2024-02-21 18:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 13:45 [PATCH] nvme-fabrics: typo in nvmf_parse_key() hare
2024-02-21 14:35 ` Chaitanya Kulkarni
2024-02-21 18:08 ` 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=ZdY8JAl921AnBWqi@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=hare@kernel.org \
    --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