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 2: fs_context
Date: Thu, 2 Oct 2025 06:57:14 +0100 [thread overview]
Message-ID: <20251002055714.GH39973@ZenIV> (raw)
A trivial D/f/porting.rst conflict...
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-fs_context
for you to fetch changes up to 57e62089f8e9d0baaba40103b167003ed7170db5:
do_nfs4_mount(): switch to vfs_parse_fs_string() (2025-09-04 15:20:58 -0400)
----------------------------------------------------------------
vfs_parse_fs_string() stuff
change on vfs_parse_fs_string() calling conventions - get rid of
the length argument (almost all callers pass strlen() of the
string argument there), add vfs_parse_fs_qstr() for the cases
that do want separate length
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
----------------------------------------------------------------
Al Viro (2):
change the calling conventions for vfs_parse_fs_string()
do_nfs4_mount(): switch to vfs_parse_fs_string()
Documentation/filesystems/mount_api.rst | 10 +++++++-
Documentation/filesystems/porting.rst | 12 +++++++++
drivers/gpu/drm/i915/gem/i915_gemfs.c | 9 ++-----
drivers/gpu/drm/v3d/v3d_gemfs.c | 9 ++-----
fs/afs/mntpt.c | 3 ++-
fs/fs_context.c | 17 ++++++-------
fs/namespace.c | 8 +++---
fs/nfs/fs_context.c | 3 +--
fs/nfs/namespace.c | 3 ++-
fs/nfs/nfs4super.c | 44 +++++++++------------------------
fs/smb/client/fs_context.c | 4 +--
include/linux/fs_context.h | 9 +++++--
kernel/trace/trace.c | 3 +--
13 files changed, 60 insertions(+), 74 deletions(-)
next reply other threads:[~2025-10-02 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 5:57 Al Viro [this message]
2025-10-03 18:41 ` [git pull] pile 2: fs_context 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=20251002055714.GH39973@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).