From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH 3/3] nvme: Put invalid namespaces on removal list
Date: Tue, 28 Jun 2016 01:32:48 -0700 [thread overview]
Message-ID: <20160628083248.GC32618@infradead.org> (raw)
In-Reply-To: <1466702946-13065-4-git-send-email-keith.busch@intel.com>
> + if (ns->ns_id > nsid) {
> + list_del_init(&ns->list);
> + list_add_tail(&ns->list, &rm_list);
> + }
This should use list_move_tail instead of the list_del_init /
list_add_tail combination.
next prev parent reply other threads:[~2016-06-28 8:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 17:29 [PATCH 0/3] Namespace iteration fixes Keith Busch
2016-06-23 17:29 ` [PATCHv2 1/3] nvme: Remove RCU namespace protection Keith Busch
2016-06-28 8:31 ` Christoph Hellwig
2016-06-28 16:35 ` Keith Busch
2016-06-30 6:48 ` Christoph Hellwig
2016-06-30 14:57 ` Keith Busch
2016-06-30 22:59 ` Keith Busch
2016-06-23 17:29 ` [PATCH 2/3] nvme: Kill detached namespaces prior to removal Keith Busch
2016-06-28 8:32 ` Christoph Hellwig
2016-06-23 17:29 ` [PATCH 3/3] nvme: Put invalid namespaces on removal list Keith Busch
2016-06-28 8:32 ` Christoph Hellwig [this message]
2016-06-23 17:44 ` [PATCH 0/3] Namespace iteration fixes Keith Busch
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=20160628083248.GC32618@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).