From: John Groves <John@Groves.net>
To: Dan Williams <dan.j.williams@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@vger.kernel.org
Cc: Jerome Glisse <jglisse@google.com>,
Christoph Hellwig <hch@infradead.org>,
John Groves <John@Groves.net>, John Groves <jgroves@micron.com>,
John Groves <John@Jagalactic.com>, John Groves <john@groves.net>
Subject: [PATCH 1/1] memremap.h: correct an error in a comment
Date: Mon, 5 Feb 2024 18:57:37 -0600 [thread overview]
Message-ID: <dba0f5f01162d6fa16e4da2a9fede7f97080e92d.1707179960.git.john@groves.net> (raw)
In-Reply-To: <cover.1707179960.git.john@groves.net>
It tried to send me off to memory_hotplug.h for an enum that is a few
lines above...
Signed-off-by: John Groves <john@groves.net>
---
include/linux/memremap.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/memremap.h b/include/linux/memremap.h
index 1314d9c5f05b..c0ad57241a9c 100644
--- a/include/linux/memremap.h
+++ b/include/linux/memremap.h
@@ -108,7 +108,7 @@ struct dev_pagemap_ops {
* @altmap: pre-allocated/reserved memory for vmemmap allocations
* @ref: reference count that pins the devm_memremap_pages() mapping
* @done: completion for @ref
- * @type: memory type: see MEMORY_* in memory_hotplug.h
+ * @type: memory type: see MEMORY_* above in memremap.h
* @flags: PGMAP_* flags to specify defailed behavior
* @vmemmap_shift: structural definition of how the vmemmap page metadata
* is populated, specifically the metadata page order.
--
2.43.0
next prev parent reply other threads:[~2024-02-06 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 0:57 [PATCH 0/1] Correct a comment in include/linux/memremap.h John Groves
2024-02-06 0:57 ` John Groves [this message]
2024-02-06 2:24 ` [PATCH 1/1] memremap.h: correct an error in a comment Dan Williams
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=dba0f5f01162d6fa16e4da2a9fede7f97080e92d.1707179960.git.john@groves.net \
--to=john@groves.net \
--cc=John@Jagalactic.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=jglisse@google.com \
--cc=jgroves@micron.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.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
all inboxes | Powered by JetHome®