All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"dwagner@suse.de" <dwagner@suse.de>
Subject: Re: [PATCH 2/3] nvmet: prevent creating ctrl with no namespace
Date: Mon, 21 Jun 2021 03:02:22 +0000	[thread overview]
Message-ID: <BYAPR04MB49652E3E4188D7FB861FE908860A9@BYAPR04MB4965.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20210618042814.GA18021@lst.de

On 6/17/21 21:28, Christoph Hellwig wrote:
> On Thu, Jun 17, 2021 at 12:06:11PM -0700, Sagi Grimberg wrote:
>> Why not just set both nn and mnan to NVMET_MAX_NAMESPACES and be done
>> with it?
> Yes, I'm pretty sure I suggested that before somewhere..
>

Sent out the patch with NVMET_MAX_NAMESPACES, please have a look.



_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2021-06-21  3:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-13 20:02 [PATCH 0/3] nvmet: use right MNAN value for controllers Chaitanya Kulkarni
2021-06-13 20:02 ` [PATCH 1/3] nvmet: use subsys->max_nsid to report MNAN Chaitanya Kulkarni
2021-06-14  6:36   ` Christoph Hellwig
2021-06-14 21:19     ` Chaitanya Kulkarni
2021-06-13 20:02 ` [PATCH 2/3] nvmet: prevent creating ctrl with no namespace Chaitanya Kulkarni
2021-06-17 19:06   ` Sagi Grimberg
2021-06-18  4:28     ` Christoph Hellwig
2021-06-21  3:02       ` Chaitanya Kulkarni [this message]
2021-06-13 20:02 ` [PATCH 3/3] nvmet: don't report subsys with 0 namespaces Chaitanya Kulkarni
2021-06-13 21:04 ` [PATCH 0/3] nvmet: use right MNAN value for controllers Chaitanya Kulkarni

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=BYAPR04MB49652E3E4188D7FB861FE908860A9@BYAPR04MB4965.namprd04.prod.outlook.com \
    --to=chaitanya.kulkarni@wdc.com \
    --cc=dwagner@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 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.