From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@meta.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de,
Keith Busch <kbusch@kernel.org>, Hannes Reinecke <hare@suse.de>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCHv2] nvme: fixup nvme auth host/target dependency
Date: Fri, 31 Oct 2025 10:58:31 +0100 [thread overview]
Message-ID: <20251031095830.GA10293@lst.de> (raw)
In-Reply-To: <20251031002655.2999568-1-kbusch@meta.com>
On Thu, Oct 30, 2025 at 05:26:55PM -0700, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> Converge the enabling of nvme-auth for both host or target into a single
> selection and implementation. The selection must inherit the strongest
> config selection of either target or host, so some Kconfig trickery is
> used to make that happen.
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
Let's see if the buildbot agrees :)
prev parent reply other threads:[~2025-10-31 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 0:26 [PATCHv2] nvme: fixup nvme auth host/target dependency Keith Busch
2025-10-31 6:57 ` Hannes Reinecke
2025-10-31 9:58 ` Christoph Hellwig [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=20251031095830.GA10293@lst.de \
--to=hch@lst.de \
--cc=hare@suse.de \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-nvme@lists.infradead.org \
--cc=lkp@intel.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;
as well as URLs for NNTP newsgroup(s).