[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <016b7cb8-451c-4d81-b3c2-e98fa0bc330a@redhat.com>
Date: Wed, 5 Mar 2025 10:53:37 +0100
From: David Hildenbrand <david@...hat.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warnings after merge of the mm tree
On 05.03.25 10:42, Stephen Rothwell wrote:
> Hi all,
>
> After merging the mm tree, today's linux-next build (htmldocs) produced
> these warnings:
>
> include/linux/mm_types.h:482: warning: Function parameter or struct member '_usable_1' not described in 'folio'
> include/linux/mm_types.h:482: warning: Function parameter or struct member '_mapcount_1' not described in 'folio'
> include/linux/mm_types.h:482: warning: Function parameter or struct member '_refcount_1' not described in 'folio'
>
> Introduced by commit
>
> bbde3b621cf7 ("mm: let _folio_nr_pages overlay memcg_data in first tail page")
>
> from the mm-unstable branch of the mm tree.
Hm, we also don't document other dummy placeholders like:
* _flags_1
* _head_1
* __page_1
So I assume there must be one way to silence these warnings, let me dig ...
--
Cheers,
David / dhildenb
Powered by blists - more mailing lists