From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL for v6.16] vfs mount api
Date: Fri, 23 May 2025 14:39:17 +0200 [thread overview]
Message-ID: <20250523-vfs-mount-api-7c425ef2eee6@brauner> (raw)
Hey Linus,
/* Summary */
This converts the bfs and omfs filesystems to the new mount api.
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit 0af2f6be1b4281385b618cb86ad946eded089ac8:
Linux 6.15-rc1 (2025-04-06 13:11:33 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.16-rc1.mount.api
for you to fetch changes up to 759cfedc5ee7e5a34fd53a4412a4645204bf7f8d:
omfs: convert to new mount API (2025-04-28 10:54:39 +0200)
Please consider pulling these changes from the signed vfs-6.16-rc1.mount.api tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.16-rc1.mount.api
----------------------------------------------------------------
Pavel Reichl (2):
bfs: convert bfs to use the new mount api
omfs: convert to new mount API
fs/bfs/inode.c | 30 +++++++---
fs/omfs/inode.c | 176 +++++++++++++++++++++++++++++++++-----------------------
2 files changed, 125 insertions(+), 81 deletions(-)
next reply other threads:[~2025-05-23 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 12:39 Christian Brauner [this message]
2025-05-26 18:35 ` [GIT PULL for v6.16] vfs mount api 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=20250523-vfs-mount-api-7c425ef2eee6@brauner \
--to=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).