From: Eric Sandeen <sandeen@redhat.com>
To: linux-mtd@lists.infradead.org
Cc: brauner@kernel.org, David Howells <dhowells@redhat.com>,
Richard Weinberger <richard@nod.at>,
Zhihao Cheng <chengzhihao1@huawei.com>
Subject: Re: [PATCH] ubifs: Convert ubifs to use the new mount API
Date: Thu, 26 Sep 2024 15:39:41 -0500 [thread overview]
Message-ID: <66f3dec2-a014-47a2-a021-a994ec41e319@redhat.com> (raw)
In-Reply-To: <20240926203604.23622-1-sandeen@redhat.com>
On 9/26/24 3:36 PM, Eric Sandeen wrote:
> From: David Howells <dhowells@redhat.com>
>
> Convert the ubifs filesystem to the new internal mount API as the old
> one will be obsoleted and removed. This allows greater flexibility in
> communication of mount parameters between userspace, the VFS and the
> filesystem.
>
> See Documentation/filesystems/mount_api.txt for more information.
>
> Signed-off-by: David Howells <dhowells@redhat.com>
> [sandeen: forward-port old patch]
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> cc: Richard Weinberger <richard@nod.at>
> cc: Zhihao Cheng <chengzhihao1@huawei.com>
> cc: linux-mtd@lists.infradead.org
Just a note, I simply picked up David's old patch from his git branch at
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/patch/?id=efee75ecdcb8f37afdedbe79a77ee571325b57d5
and forward-ported it. It's build tested only, so review and testing
would be most appreciated.
Aside from some minor changes to the internal mount API that
required adjustment, there was also a new compression type and a couple
additional ubifs_info members that needed initialization in
ubifs_init_fs_context.
Thanks!
-Eric
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2024-09-26 20:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 20:36 [PATCH] ubifs: Convert ubifs to use the new mount API Eric Sandeen
2024-09-26 20:39 ` Eric Sandeen [this message]
2024-09-27 7:47 ` Christian Brauner
2024-09-27 14:12 ` Zhihao Cheng
2024-09-27 14:15 ` Zhihao Cheng
2024-09-27 15:56 ` Eric Sandeen
2024-09-29 1:57 ` Zhihao Cheng
2024-09-29 2:03 ` Zhihao Cheng
2024-09-29 16:46 ` Eric Sandeen
2024-09-30 1:22 ` Zhihao Cheng
2024-10-01 20:20 ` Eric Sandeen
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=66f3dec2-a014-47a2-a021-a994ec41e319@redhat.com \
--to=sandeen@redhat.com \
--cc=brauner@kernel.org \
--cc=chengzhihao1@huawei.com \
--cc=dhowells@redhat.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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