From: Balbir Singh <balbirs@nvidia•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Andrew Morton <akpm@linux-foundation•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the mm-unstable tree
Date: Fri, 12 Sep 2025 14:58:58 +1000 [thread overview]
Message-ID: <2f0f8adf-03ef-49db-9e78-9a565154cb2d@nvidia.com> (raw)
In-Reply-To: <20250912141232.17bd512f@canb.auug.org.au>
On 9/12/25 14:12, Stephen Rothwell wrote:
> Hi all,
>
> After merging the mm-unstable tree, today's linux-next build (htmldocs)
> produced this warning:
>
> WARNING: mm/migrate_device.c:792 function parameter 'page' not described in 'migrate_vma_insert_huge_pmd_page'
>
> Introduced by commit
>
> 9a5e80c43c9e ("mm/migrate_device: implement THP migration of zone device pages")
>
Thanks, the parameter is incorrectly described as folio, will fix
Balbir
next prev parent reply other threads:[~2025-09-12 4:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 4:12 linux-next: build warning after merge of the mm-unstable tree Stephen Rothwell
2025-09-12 4:58 ` Balbir Singh [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-07 3:39 Stephen Rothwell
2025-11-07 6:51 ` Randy Dunlap
2025-10-20 2:49 Stephen Rothwell
2025-10-20 2:45 Stephen Rothwell
2025-10-20 3:41 ` Baoquan He
2025-10-20 4:19 ` Bagas Sanjaya
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:54 Stephen Rothwell
2025-07-10 22:30 ` Andrew Morton
2025-07-10 22:49 ` Stephen Rothwell
2025-07-11 0:36 ` Randy Dunlap
2025-07-11 6:28 ` David Hildenbrand
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=2f0f8adf-03ef-49db-9e78-9a565154cb2d@nvidia.com \
--to=balbirs@nvidia$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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