From: SJ Park <sj@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: SJ Park <sj@kernel.org>,
linux-mm@kvack.org, Shivank Garg <shivankg@amd.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm/migrate: add missing kernel-doc for @migrate_info
Date: Fri, 17 Jul 2026 17:08:06 -0700 [thread overview]
Message-ID: <20260718000807.85807-1-sj@kernel.org> (raw)
In-Reply-To: <20260717022146.1290242-1-rdunlap@infradead.org>
On Thu, 16 Jul 2026 19:21:46 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
> 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'
Nice catch!
>
> 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>
Btw, get_maintainer.pl suggests adding below more recipients to this patch. I
guess they were intentionally not Cc-ed since this is a simple change. And I
think that's fair enough. Just wanted to call out for a case.
- David Hildenbrand <david@kernel.org>
- Lorenzo Stoakes <ljs@kernel.org>
- "Liam R. Howlett" <liam@infradead.org>
- Vlastimil Babka <vbabka@kernel.org>
- Mike Rapoport <rppt@kernel.org>
- Suren Baghdasaryan <surenb@google.com>
- Michal Hocko <mhocko@suse.com>
- Huang Ying <ying.huang@linux.alibaba.com>
- Zi Yan <ziy@nvidia.com>
- Jonathan Cameron <jic23@kernel.org>
- linux-kernel@vger.kernel.org
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-07-18 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 2:21 [PATCH] mm/migrate: add missing kernel-doc for @migrate_info Randy Dunlap
2026-07-18 0:08 ` SJ Park [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=20260718000807.85807-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=shivankg@amd.com \
/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