From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,sj@kernel.org,shivankg@amd.com,rdunlap@infradead.org,akpm@linux-foundation.org
Subject: [folded-merged] mm-migrate-use-migrate_info-field-instead-of-private-fix.patch removed from -mm tree
Date: Tue, 28 Jul 2026 20:51:24 -0700 [thread overview]
Message-ID: <20260729035124.DAD401F000E9@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/migrate: add missing kernel-doc for @migrate_info
has been removed from the -mm tree. Its filename was
mm-migrate-use-migrate_info-field-instead-of-private-fix.patch
This patch was dropped because it was folded into mm-migrate-use-migrate_info-field-instead-of-private.patch
------------------------------------------------------
From: Randy Dunlap <rdunlap@infradead.org>
Subject: mm/migrate: add missing kernel-doc for @migrate_info
Date: Thu, 16 Jul 2026 19:21:46 -0700
Add a kernel-doc comment for @migrate_info so that kernel-doc won't
produce a warning about it:
WARNING: include/linux/mm_types.h:507 struct member 'migrate_info' not described in 'folio'
Link: https://lore.kernel.org/20260717022146.1290242-1-rdunlap@infradead.org
Fixes: f3768940afdc ("mm/migrate: use migrate_info field instead of private")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Reviewed-by: SJ Park <sj@kernel.org>
Reviewed-by: Shivank Garg <shivankg@amd.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/mm_types.h | 2 ++
1 file changed, 2 insertions(+)
--- a/include/linux/mm_types.h~mm-migrate-use-migrate_info-field-instead-of-private-fix
+++ a/include/linux/mm_types.h
@@ -368,6 +368,8 @@ typedef unsigned short mm_id_t;
* dax_associate_entry.
* @private: Filesystem per-folio data (see folio_attach_private()).
* @swap: Used for swp_entry_t if folio_test_swapcache().
+ * @migrate_info: Stores migration state (anon_vma pointer and
+ * FOLIO_WAS_* markers).
* @_mapcount: Do not access this member directly. Use folio_mapcount() to
* find out how many times this folio is mapped by userspace.
* @_refcount: Do not access this member directly. Use folio_ref_count()
_
Patches currently in -mm which might be from rdunlap@infradead.org are
mm-migrate-use-migrate_info-field-instead-of-private.patch
mm-page_owner-document-page_owner-filter-fix.patch
radix-tree-add-correct-some-kernel-doc.patch
delaytop-sort-by-max-delay-to-highlight-top-latency-processes-fix.patch
rbtree-fixup-kernel-doc-names.patch
llist-use-correct-function-parameter-name.patch
stacktrace-header-repair-kernel-doc-comments.patch
reply other threads:[~2026-07-29 3:51 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=20260729035124.DAD401F000E9@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=shivankg@amd.com \
--cc=sj@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.