From: Christian Brauner <brauner@kernel.org>
To: linux-fsdevel@vger.kernel.org, Eric Sandeen <sandeen@redhat.com>
Cc: Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH 0/5] adfs, affs, befs, hfs, hfsplus: convert to new mount api
Date: Wed, 18 Sep 2024 11:46:06 +0200 [thread overview]
Message-ID: <20240918-geblickt-tapir-f7d341aaeaa7@brauner> (raw)
In-Reply-To: <20240916172735.866916-1-sandeen@redhat.com>
On Mon, 16 Sep 2024 13:26:17 -0400, Eric Sandeen wrote:
> These were all tested against images I created or obtained, using a
> script to test random combinations of valid and invalid mount and
> remount options, and comparing the results before and after the changes.
>
> AFAICT, all parsing works as expected and behavior is unchanged.
>
> (Changes since first send: fixing a couple string leaks, added hfs
> and hfsplus.)
>
> [...]
Applied to the vfs.mount.api.v6.13 branch of the vfs/vfs.git tree.
Patches in the vfs.mount.api.v6.13 branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.mount.api.v6.13
[1/5] adfs: convert adfs to use the new mount api
https://git.kernel.org/vfs/vfs/c/5fadeed64d27
[2/5] affs: convert affs to use the new mount api
https://git.kernel.org/vfs/vfs/c/de25e36d83fc
[3/5] befs: convert befs to use the new mount api
https://git.kernel.org/vfs/vfs/c/c3099e72bf4f
[4/5] hfs: convert hfs to use the new mount api
https://git.kernel.org/vfs/vfs/c/c87d1f1aa91c
[5/5] hfsplus: convert hfsplus to use the new mount api
https://git.kernel.org/vfs/vfs/c/3c8fb5d57b49
prev parent reply other threads:[~2024-09-18 9:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 17:26 [PATCH 0/5] adfs, affs, befs, hfs, hfsplus: convert to new mount api Eric Sandeen
2024-09-16 17:26 ` [PATCH 1/5] adfs: convert adfs to use the " Eric Sandeen
2024-09-17 12:52 ` Jan Kara
2024-09-16 17:26 ` [PATCH 2/5] affs: convert affs " Eric Sandeen
2024-09-17 12:51 ` Jan Kara
2024-09-17 14:53 ` [PATCH 2/5 V2] " Eric Sandeen
2024-09-17 15:37 ` David Sterba
2024-09-16 17:26 ` [PATCH 3/5] befs: convert befs " Eric Sandeen
2024-09-17 15:50 ` Jan Kara
2024-09-16 17:26 ` [PATCH 4/5] hfs: convert hfs " Eric Sandeen
2024-09-17 15:55 ` Jan Kara
2024-09-16 17:26 ` [PATCH 5/5] hfsplus: convert hfsplus " Eric Sandeen
2024-09-17 16:11 ` Jan Kara
2024-09-18 9:46 ` Christian Brauner [this message]
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=20240918-geblickt-tapir-f7d341aaeaa7@brauner \
--to=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@redhat.com \
/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).