From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
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: Thu, 6 Nov 2025 22:51:37 -0800 [thread overview]
Message-ID: <cc5fa7f1-1f3a-4dfc-81c0-fe69b5f4cd4b@infradead.org> (raw)
In-Reply-To: <20251107143908.48e3e29e@canb.auug.org.au>
On 11/6/25 7:39 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the mm-unstable tree, today's linux-next build (htmldocs)
> produced this warning:
>
> WARNING: include/linux/mm_types.h:302 cannot understand function prototype: 'typedef swp_entry_t leaf_entry_t;'
>
> Introduced by commit
>
> 1b8c333c0d1c ("mm-introduce-leaf-entry-type-and-use-to-simplify-leaf-entry-logic-fix")
>
Change the kernel-doc comment beginning to:
/**
* typedef leaf_entry_t - Describes a page table 'leaf entry'.
--
~Randy
next prev parent reply other threads:[~2025-11-07 6:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 3:39 Stephen Rothwell
2025-11-07 6:51 ` Randy Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
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-12 4:12 Stephen Rothwell
2025-09-12 4:58 ` Balbir Singh
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=cc5fa7f1-1f3a-4dfc-81c0-fe69b5f4cd4b@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®