From: Christian Brauner <brauner@kernel.org>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Eric Sandeen <sandeen@redhat.com>
Cc: Christian Brauner <brauner@kernel.org>, Tyler Hicks <code@tyhicks.com>
Subject: Re: [PATCH] ecryptfs: remove NULL remount_fs from super_operations
Date: Sat, 1 Mar 2025 10:28:34 +0100 [thread overview]
Message-ID: <20250301-latten-unlogisch-7a59c9bcf245@brauner> (raw)
In-Reply-To: <5dc2eb45-7126-4777-a7f9-29d02dff443f@redhat.com>
On Fri, 28 Feb 2025 08:31:17 -0600, Eric Sandeen wrote:
> This got missed during the mount API conversion. This makes no functional
> difference, but after we convert the last filesystem, we'll want to remove
> the remount_fs op from super_operations altogether. So let's just get this
> out of the way now.
>
>
Applied to the vfs-6.15.misc branch of the vfs/vfs.git tree.
Patches in the vfs-6.15.misc 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-6.15.misc
[1/1] ecryptfs: remove NULL remount_fs from super_operations
https://git.kernel.org/vfs/vfs/c/46bbe45bef93
next prev parent reply other threads:[~2025-03-01 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 14:31 [PATCH] ecryptfs: remove NULL remount_fs from super_operations Eric Sandeen
2025-03-01 9:28 ` Christian Brauner [this message]
2025-03-03 15:49 ` Tyler Hicks
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=20250301-latten-unlogisch-7a59c9bcf245@brauner \
--to=brauner@kernel.org \
--cc=code@tyhicks.com \
--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).