From: Christoph Hellwig <hch@lst.de>
To: Max Gurtovoy <mgurtovoy@nvidia.com>
Cc: hch@lst.de, linux-nvme@lists.infradead.org, kbusch@kernel.org,
sagi@grimberg.me, kch@nvidia.com, israelr@nvidia.com
Subject: Re: [PATCH 1/1] nvmet: remove redundant subsysnqn field from ctrl
Date: Fri, 3 Oct 2025 09:25:42 +0200 [thread overview]
Message-ID: <20251003072542.GA12624@lst.de> (raw)
In-Reply-To: <20250924203402.10688-1-mgurtovoy@nvidia.com>
On Wed, Sep 24, 2025 at 11:34:02PM +0300, Max Gurtovoy wrote:
> #ifdef CONFIG_NVME_TARGET_TCP_TLS
> - tls_key = nvme_tls_psk_refresh(NULL, sq->ctrl->hostnqn, sq->ctrl->subsysnqn,
> + tls_key = nvme_tls_psk_refresh(NULL, sq->ctrl->hostnqn, sq->ctrl->subsys->subsysnqn,
Please fix the overly long line here (and in the next line) while touching
this.
next prev parent reply other threads:[~2025-10-03 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 20:34 [PATCH 1/1] nvmet: remove redundant subsysnqn field from ctrl Max Gurtovoy
2025-09-24 22:14 ` Keith Busch
2025-10-03 7:25 ` Christoph Hellwig [this message]
2025-10-08 11:37 ` Max Gurtovoy
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=20251003072542.GA12624@lst.de \
--to=hch@lst.de \
--cc=israelr@nvidia.com \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mgurtovoy@nvidia.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