From: David Howells <dhowells@redhat.com>
To: viro@zeniv.linux.org.uk
Cc: linux-block@vger.kernel.org,
squashfs-devel@lists.sourceforge.net,
Richard Weinberger <richard@nod.at>,
Marek Vasut <marek.vasut@gmail.com>,
Brian Norris <computersforpeace@gmail.com>,
Nicolas Pitre <nico@linaro.org>,
Boris Brezillon <bbrezillon@kernel.org>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Phillip Lougher <phillip@squashfs.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
dhowells@redhat.com
Subject: [RFC PATCH 0/6] mtd, romfs, cramfs, jffs2, squashfs: Convert to fs_context
Date: Thu, 21 Mar 2019 11:51:58 +0000 [thread overview]
Message-ID: <155316911807.30162.12050856576466287021.stgit@warthog.procyon.org.uk> (raw)
Hi Al,
Here's a set of patches that convert romfs, cramfs, jffs2 and squashfs to
use the new fs_context struct and replace mount_mtd(). They have
prerequisite commits (such as replacing mount_bdev()) that can be found in
the branch detailed below.
(1) Provide a replacement for mount_mtd() that takes an fs_context to
specify the parameters.
I also put an mtd device pointer into the fs_context struct for use in
the sget_fc() test and set functions plus a destructor because
put_fs_context() can't reach into the mtd module.
(2) Convert romfs.
(3) Convert cramfs.
(4) Convert jffs2.
(5) Get rid of the now-obsolete mount_mtd() function.
(6) Convert squashfs.
These can be found in the following branch:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=mount-api-viro
Thanks,
David
---
David Howells (6):
mtd: Provide fs_context-aware mount_mtd() replacement
romfs: Convert to fs_context
cramfs: Convert to fs_context
jffs2: Convert to fs_context
mtd: Kill off mount_mtd()
squashfs: Convert to fs_context
drivers/mtd/mtdcore.h | 1
drivers/mtd/mtdsuper.c | 181 ++++++++++++++++++++++----------------------
fs/cramfs/inode.c | 69 +++++++++--------
fs/fs_context.c | 2
fs/jffs2/fs.c | 21 +++--
fs/jffs2/os-linux.h | 4 -
fs/jffs2/super.c | 172 ++++++++++++++++++++----------------------
fs/romfs/super.c | 46 +++++++----
fs/squashfs/super.c | 100 +++++++++++++-----------
include/linux/fs_context.h | 2
include/linux/mtd/super.h | 6 +
11 files changed, 316 insertions(+), 288 deletions(-)
next reply other threads:[~2019-03-21 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 11:51 David Howells [this message]
2019-03-21 11:52 ` [RFC PATCH 1/6] mtd: Provide fs_context-aware mount_mtd() replacement David Howells
2019-03-21 11:52 ` [RFC PATCH 2/6] romfs: Convert to fs_context David Howells
2019-03-21 11:52 ` [RFC PATCH 3/6] cramfs: " David Howells
2019-03-21 11:52 ` [RFC PATCH 4/6] jffs2: " David Howells
2019-03-21 11:52 ` [RFC PATCH 5/6] mtd: Kill off mount_mtd() David Howells
2019-03-21 11:53 ` [RFC PATCH 6/6] squashfs: Convert to fs_context David Howells
-- strict thread matches above, loose matches on Subject: below --
2019-03-20 14:44 [RFC PATCH 0/6] mtd, romfs, cramfs, jffs2, " David Howells
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=155316911807.30162.12050856576466287021.stgit@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=nico@linaro.org \
--cc=phillip@squashfs.org.uk \
--cc=richard@nod.at \
--cc=squashfs-devel@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
/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).