From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Christian Brauner <brauner@kernel•org>
Cc: Mateusz Guzik <mjguzik@gmail•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build warnings after merge of the vfs-brauner tree
Date: Wed, 12 Nov 2025 13:42:42 +1100 [thread overview]
Message-ID: <20251112134242.2608a613@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
Hi all,
After merging the vfs-brauner tree, today's linux-next build (htmldocs)
produced these warnings:
WARNING: fs/namei.c:627 function parameter 'idmap' not described in 'lookup_inode_permission_may_exec'
WARNING: fs/namei.c:627 function parameter 'inode' not described in 'lookup_inode_permission_may_exec'
WARNING: fs/namei.c:627 function parameter 'mask' not described in 'lookup_inode_permission_may_exec'
Introduced by commit
5ecf656231cc ("fs: speed up path lookup with cheaper handling of MAY_EXEC")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-11-12 2:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 2:42 Stephen Rothwell [this message]
2025-11-12 10:10 ` linux-next: build warnings after merge of the vfs-brauner tree Mateusz Guzik
2025-11-12 10:55 ` Stephen Rothwell
2025-11-12 10:57 ` Mateusz Guzik
-- strict thread matches above, loose matches on Subject: below --
2025-12-16 0:52 Stephen Rothwell
2025-11-17 6:47 Stephen Rothwell
2025-07-17 7:36 Stephen Rothwell
2025-07-22 10:24 ` Jann Horn
2025-03-05 10:07 Stephen Rothwell
2025-03-05 10:55 ` David Disseldorp
2024-12-13 4:27 Stephen Rothwell
2024-12-19 6:32 ` Stephen Rothwell
2025-01-14 5:48 ` Stephen Rothwell
2025-01-20 8:25 ` Stephen Rothwell
2025-01-20 12:15 ` Christian Brauner
2025-01-20 20:55 ` Stephen Rothwell
2024-12-11 3:37 Stephen Rothwell
2024-12-19 6:31 ` Stephen Rothwell
2024-12-19 12:40 ` Jeff Layton
2024-12-19 20:36 ` Stephen Rothwell
2025-01-06 13:50 ` Geert Uytterhoeven
2024-10-09 6:29 Stephen Rothwell
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=20251112134242.2608a613@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=brauner@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mjguzik@gmail$(echo .)com \
/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