From: Christian Brauner Date: Fri, 31 Jul 2026 08:37:40 +0000 (+0200) Subject: Merge patch series "fs/namei.c: comment and coding style fixups" X-Git-Url: http://git.ipfire.org/gitweb/index.cgi?a=commitdiff_plain;h=895741772f6ca989da565bcbe4673f12d3d0ac31;p=thirdparty%2Flinux.git Merge patch series "fs/namei.c: comment and coding style fixups" Christian Brauner says: Three comment and coding style fixups for your lookup_open() rework and Jori's audit series as they sit in vfs-7.3.lookup. No functional changes. * Update the comments above lookup_open(). It takes the parent inode lock itself now but the comment still tells the caller to take it. A caller following it deadlocks and the series added a second caller. The claim that it returns 0 and updates @path goes as well, that one has been wrong since v5.7. * Give the return description of atomic_open() the colon that kernel-doc needs. Without it the description is dropped and W=1 warns about it. The summary line has to stand on its own line too, so the "from a negative dentry" part moves into the body. * Fix a space indented continuation line, three declarations without a following blank line and a trailing */ on the last line of a block comment. * patches from https://patch.msgid.link/20260731-work-lookup-fixes-v1-0-2412b85cf65c@kernel.org: fs/namei.c: fix coding style in atomic_open() and lookup_open() fs/namei.c: fix kerneldoc of atomic_open() and vfs_lookup_open() fs/namei.c: update stale comments in lookup_open() Link: https://patch.msgid.link/20260731-work-lookup-fixes-v1-0-2412b85cf65c@kernel.org Signed-off-by: Christian Brauner (Amutable) --- 895741772f6ca989da565bcbe4673f12d3d0ac31