From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,john@groves.net,hch@infradead.org,dan.j.williams@intel.com,John@Groves.net,akpm@linux-foundation.org
Subject: [merged mm-stable] memremaph-correct-an-error-in-a-comment.patch removed from -mm tree
Date: Wed, 21 Feb 2024 16:03:23 -0800 [thread overview]
Message-ID: <20240222000323.F13FCC43390@smtp.kernel.org> (raw)
The quilt patch titled
Subject: memremap.h: correct an error in a comment
has been removed from the -mm tree. Its filename was
memremaph-correct-an-error-in-a-comment.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: John Groves <John@Groves.net>
Subject: memremap.h: correct an error in a comment
Date: Mon, 5 Feb 2024 18:57:37 -0600
It tried to send me off to memory_hotplug.h for an enum that is a few
lines above...
Link: https://lkml.kernel.org/r/dba0f5f01162d6fa16e4da2a9fede7f97080e92d.1707179960.git.john@groves.net
Signed-off-by: John Groves <john@groves.net>
Reviewed-by: Dan Williams <dan.j.williams@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/memremap.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/include/linux/memremap.h~memremaph-correct-an-error-in-a-comment
+++ a/include/linux/memremap.h
@@ -109,7 +109,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.
_
Patches currently in -mm which might be from John@Groves.net are
reply other threads:[~2024-02-22 0:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240222000323.F13FCC43390@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=john@groves.net \
--cc=mm-commits@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 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.