From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, Christian Brauner <brauner@kernel.org>
Subject: [git pull] pile 4: finish_no_open()
Date: Thu, 2 Oct 2025 07:02:28 +0100 [thread overview]
Message-ID: <20251002060228.GJ39973@ZenIV> (raw)
The following changes since commit 76eeb9b8de9880ca38696b2fb56ac45ac0a25c6c:
Linux 6.17-rc5 (2025-09-07 14:22:57 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-finish_no_open
for you to fetch changes up to 2944ebee9a96c9d2ddb9c9cb99df6105f2de62ff:
slightly simplify nfs_atomic_open() (2025-09-16 23:59:38 -0400)
----------------------------------------------------------------
finish_no_open calling conventions change
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
----------------------------------------------------------------
Al Viro (9):
allow finish_no_open(file, ERR_PTR(-E...))
9p: simplify v9fs_vfs_atomic_open()
9p: simplify v9fs_vfs_atomic_open_dotl()
simplify cifs_atomic_open()
simplify vboxsf_dir_atomic_open()
simplify nfs_atomic_open_v23()
simplify fuse_atomic_open()
simplify gfs2_atomic_open()
slightly simplify nfs_atomic_open()
fs/9p/vfs_inode.c | 34 ++++++++++++----------------------
fs/9p/vfs_inode_dotl.c | 15 +++++----------
fs/fuse/dir.c | 21 +++++++--------------
fs/gfs2/inode.c | 26 +++++++++-----------------
fs/nfs/dir.c | 18 +++++-------------
fs/open.c | 10 ++++++----
fs/smb/client/dir.c | 8 +-------
fs/vboxsf/dir.c | 25 +++++++++----------------
8 files changed, 54 insertions(+), 103 deletions(-)
next reply other threads:[~2025-10-02 6:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 6:02 Al Viro [this message]
2025-10-03 18:41 ` [git pull] pile 4: finish_no_open() pr-tracker-bot
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=20251002060228.GJ39973@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).