From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 2/3] nvmet: expose discovery subsystems
Date: Thu, 7 Apr 2022 11:45:37 +0200 [thread overview]
Message-ID: <20220407094537.GA23413@lst.de> (raw)
In-Reply-To: <20220406142210.71248-3-hare@suse.de>
On Wed, Apr 06, 2022 at 04:22:09PM +0200, Hannes Reinecke wrote:
> Add a module parameter 'expose_discovery_subsys' to allow creation
> of discovery subsystems through configfs.
> If the option is enabled no default discovery subsystem is created
> per default, and the user is required to create one via configfs.
I'm not fan of module parameters. Can we do this using configfs on a
per-port basis?
next prev parent reply other threads:[~2022-04-07 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 14:22 [PATCHv3 0/3] nvmet: unique discovery subsystem Hannes Reinecke
2022-04-06 14:22 ` [PATCH 1/3] nvmet: make the subsystem type configurable Hannes Reinecke
2022-04-06 14:22 ` [PATCH 2/3] nvmet: expose discovery subsystems Hannes Reinecke
2022-04-07 9:45 ` Christoph Hellwig [this message]
2022-04-07 10:13 ` Hannes Reinecke
2022-04-06 14:22 ` [PATCH 3/3] nvmet: include all configured port in the discovery log page Hannes Reinecke
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=20220407094537.GA23413@lst.de \
--to=hch@lst.de \
--cc=hare@suse.de \
--cc=kbusch@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.