diff options
| author | Christian Brauner <brauner@kernel.org> | 2026-07-31 10:37:40 +0200 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2026-07-31 10:37:40 +0200 |
| commit | 895741772f6ca989da565bcbe4673f12d3d0ac31 (patch) | |
| tree | 47f60c5cea53771e8a53a732e5d45cd2b957df08 /drivers/phy/axiado/git@git.tavy.me:linux.git | |
| parent | b2f1e6301efa4a80becdb0715416c3cbc693fbb4 (diff) | |
| parent | b89b75f362518c7555f67d38774194832304471b (diff) | |
Merge patch series "fs/namei.c: comment and coding style fixups"
Christian Brauner <brauner@kernel.org> 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) <brauner@kernel.org>
Diffstat (limited to 'drivers/phy/axiado/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions
