From: Matthew Sakai <msakai@redhat.com>
To: dm-devel@lists.linux.dev
Cc: Matthew Sakai <msakai@redhat.com>
Subject: [PATCH 11/11] dm vdo: remove outdated pointer_map reference
Date: Thu, 29 Feb 2024 23:26:29 -0500 [thread overview]
Message-ID: <cc2dbdc9254cf4ff4efe1dc50cf7c132069fbe6e.1709266694.git.msakai@redhat.com> (raw)
In-Reply-To: <cover.1709266694.git.msakai@redhat.com>
Signed-off-by: Matthew Sakai <msakai@redhat.com>
---
drivers/md/dm-vdo/vdo.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/md/dm-vdo/vdo.c b/drivers/md/dm-vdo/vdo.c
index c161dffeb91a..d16404588881 100644
--- a/drivers/md/dm-vdo/vdo.c
+++ b/drivers/md/dm-vdo/vdo.c
@@ -67,10 +67,7 @@ struct sync_completion {
struct completion completion;
};
-/*
- * We don't expect this set to ever get really large, so a linked list is adequate. We can use a
- * pointer_map if we need to later.
- */
+/* A linked list is adequate for the small number of entries we expect. */
struct device_registry {
struct list_head links;
/* TODO: Convert to rcu per kernel recommendation. */
--
2.42.0
prev parent reply other threads:[~2024-03-01 4:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 4:26 [PATCH 00/11] dm vdo: fix minor comment issues Matthew Sakai
2024-03-01 4:26 ` [PATCH 01/11] dm vdo: Modify mismatched function name Matthew Sakai
2024-03-01 4:26 ` [PATCH 02/11] dm vdo slab-depot: " Matthew Sakai
2024-03-01 4:26 ` [PATCH 03/11] dm vdo: " Matthew Sakai
2024-03-01 4:26 ` [PATCH 04/11] " Matthew Sakai
2024-03-01 4:26 ` [PATCH 05/11] " Matthew Sakai
2024-03-01 4:26 ` [PATCH 06/11] " Matthew Sakai
2024-03-01 4:26 ` [PATCH 07/11] dm vdo dedupe: " Matthew Sakai
2024-03-01 4:26 ` [PATCH 08/11] dm vdo: " Matthew Sakai
2024-03-01 4:26 ` [PATCH 09/11] dm vdo indexer delta-index: fix typos in comments Matthew Sakai
2024-03-01 4:26 ` [PATCH 10/11] dm vdo: update module comments Matthew Sakai
2024-03-01 4:26 ` Matthew Sakai [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=cc2dbdc9254cf4ff4efe1dc50cf7c132069fbe6e.1709266694.git.msakai@redhat.com \
--to=msakai@redhat.com \
--cc=dm-devel@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).