From: Keith Busch <kbusch@kernel.org>
To: Max Gurtovoy <mgurtovoy@nvidia.com>
Cc: hch@lst.de, linux-nvme@lists.infradead.org, sagi@grimberg.me,
kch@nvidia.com, israelr@nvidia.com
Subject: Re: [PATCH 1/1] nvmet: remove redundant subsysnqn field from ctrl
Date: Wed, 24 Sep 2025 16:14:16 -0600 [thread overview]
Message-ID: <aNRtOKEmWMYrDT6-@kbusch-mbp> (raw)
In-Reply-To: <20250924203402.10688-1-mgurtovoy@nvidia.com>
On Wed, Sep 24, 2025 at 11:34:02PM +0300, Max Gurtovoy wrote:
> The subsysnqn field in the nvmet controller structure is redundant,
> since the subsystem NQN can always be accessed via the controller's
> subsystem reference. Remove this field to save memory and avoid
> unnecessary duplication.
Looks good, applied to nvme-6.18.
next prev parent reply other threads:[~2025-09-24 22:14 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 [this message]
2025-10-03 7:25 ` Christoph Hellwig
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=aNRtOKEmWMYrDT6-@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=hch@lst.de \
--cc=israelr@nvidia.com \
--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