From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Hildenbrand <david@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the mm-unstable tree
Date: Thu, 10 Jul 2025 17:54:46 +1000 [thread overview]
Message-ID: <20250710175446.128c7def@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
Hi all,
After merging the mm-unstable tree, today's linux-next build (htmldocs)
produced this warning:
mm/migrate.c:215: warning: Function parameter or struct member 'dst' not described in 'migrate_movable_ops_page'
mm/migrate.c:215: warning: Function parameter or struct member 'src' not described in 'migrate_movable_ops_page'
mm/migrate.c:215: warning: Function parameter or struct member 'mode' not described in 'migrate_movable_ops_page'
mm/migrate.c:215: warning: Excess function parameter 'page' description in 'migrate_movable_ops_page'
Introduced by commit
d5967fb0bf8e ("mm/migrate: factor out movable_ops page handling into migrate_movable_ops_page()")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-07-10 7:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 7:54 Stephen Rothwell [this message]
2025-07-10 22:30 ` linux-next: build warning after merge of the mm-unstable tree Andrew Morton
2025-07-10 22:49 ` Stephen Rothwell
2025-07-11 0:36 ` Randy Dunlap
2025-07-11 6:28 ` David Hildenbrand
-- strict thread matches above, loose matches on Subject: below --
2025-09-04 2:14 Stephen Rothwell
2025-09-04 2:59 ` Andrew Morton
2025-09-04 6:33 ` David Hildenbrand
2025-07-15 8:55 Stephen Rothwell
2025-07-15 18:54 ` SeongJae Park
2025-07-10 7:50 Stephen Rothwell
2025-07-11 9:57 ` David Hildenbrand
2025-06-10 4:33 Stephen Rothwell
2025-06-10 4:35 ` Christoph Hellwig
2025-05-09 9:43 Stephen Rothwell
2025-05-09 20:31 ` Andrew Morton
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=20250710175446.128c7def@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).