From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] several more mount API conversions
Date: Mon, 23 Sep 2019 20:21:47 +0100 [thread overview]
Message-ID: <20190923192147.GC26530@ZenIV.linux.org.uk> (raw)
Assorted conversions of options parsing to new API.
gfs2 is probably the most serious one here; the rest is
trivial stuff. Other things in what used to be #work.mount
are going to wait for the next cycle (and preferably go via
git trees of the filesystems involved).
The following changes since commit 74983ac20aeafc88d9ceed64a8bf2a9024c488d5:
vfs: Make fs_parse() handle fs_param_is_fd-type params better (2019-09-12 21:06:14 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.mount3
for you to fetch changes up to 1f52aa08d12f8d359e71b4bfd73ca9d5d668e4da:
gfs2: Convert gfs2 to fs_context (2019-09-18 22:47:05 -0400)
----------------------------------------------------------------
Andrew Price (1):
gfs2: Convert gfs2 to fs_context
David Howells (5):
vfs: Convert bpf to use the new mount API
vfs: Convert functionfs to use the new mount API
hypfs: Fix error number left in struct pointer member
vfs: Convert hypfs to use the new mount API
vfs: Convert spufs to use the new mount API
arch/powerpc/platforms/cell/spufs/inode.c | 207 +++++++------
arch/s390/hypfs/inode.c | 137 +++++----
drivers/usb/gadget/function/f_fs.c | 233 +++++++-------
fs/gfs2/incore.h | 8 +-
fs/gfs2/ops_fstype.c | 495 ++++++++++++++++++++++--------
fs/gfs2/super.c | 333 +-------------------
fs/gfs2/super.h | 3 +-
kernel/bpf/inode.c | 92 ++++--
8 files changed, 749 insertions(+), 759 deletions(-)
next reply other threads:[~2019-09-23 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 19:21 Al Viro [this message]
2019-09-24 19:55 ` [git pull] several more mount API conversions pr-tracker-bot
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=20190923192147.GC26530@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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