From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH v2] nvme/target: Change max_nsid in subsystem due to ns_disable if needed
Date: Thu, 19 Oct 2017 02:01:22 -0700 [thread overview]
Message-ID: <20171019090122.GB4974@infradead.org> (raw)
In-Reply-To: <1508323567-8536-1-git-send-email-sagi@grimberg.me>
> + if (list_empty(&subsys->namespaces)) {
> + subsys->max_nsid = 0;
> + } else {
> + struct nvmet_ns *ns =
> + list_last_entry(&subsys->namespaces, struct nvmet_ns, dev_link);
> +
> + subsys->max_nsid = ns->nsid;
> + }
The line is still too long, but I'll fix it up.
prev parent reply other threads:[~2017-10-19 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 10:46 [PATCH v2] nvme/target: Change max_nsid in subsystem due to ns_disable if needed Sagi Grimberg
2017-10-18 11:12 ` Johannes Thumshirn
2017-10-19 9:01 ` 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=20171019090122.GB4974@infradead.org \
--to=hch@infradead.org \
/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).