linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tyler Hicks <code@tyhicks.com>
To: Eric Sandeen <sandeen@redhat.com>,
	Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] ecryptfs: remove NULL remount_fs from super_operations
Date: Mon, 3 Mar 2025 09:49:28 -0600	[thread overview]
Message-ID: <Z8XPiCF4SkjY5uw0@redbud> (raw)
In-Reply-To: <5dc2eb45-7126-4777-a7f9-29d02dff443f@redhat.com>

On 2025-02-28 08:31:17, 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.
> 
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>

Acked-by: Tyler Hicks <code@tyhicks.com>

Thanks for picking it up, Christian.

Tyler

> ---
> 
> diff --git a/fs/ecryptfs/super.c b/fs/ecryptfs/super.c
> index 0b1c878317ab..e7b7f426fecf 100644
> --- a/fs/ecryptfs/super.c
> +++ b/fs/ecryptfs/super.c
> @@ -172,7 +172,6 @@ const struct super_operations ecryptfs_sops = {
>  	.destroy_inode = ecryptfs_destroy_inode,
>  	.free_inode = ecryptfs_free_inode,
>  	.statfs = ecryptfs_statfs,
> -	.remount_fs = NULL,
>  	.evict_inode = ecryptfs_evict_inode,
>  	.show_options = ecryptfs_show_options
>  };
> 

      parent reply	other threads:[~2025-03-03 15:49 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
2025-03-03 15:49 ` Tyler Hicks [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=Z8XPiCF4SkjY5uw0@redbud \
    --to=code@tyhicks.com \
    --cc=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).