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] vboxsf
Date: Sat, 8 Feb 2020 22:46:37 +0000 [thread overview]
Message-ID: <20200208224637.GH23230@ZenIV.linux.org.uk> (raw)
vboxsf, with fixups for fs_parse changes folded in. Identical to what
had been in -next - git diff work.vboxsf merge.nfs-fs_parse comes empty.
It is a rebase (on top of merge.nfs-fs_parse.1), but it's a single commit
and here the tree being identical to what had been tested is all that
matters - feeding it in two chunks (original commit + fixups) would be
completely pointless, IMO. That should be it for bisect hazards from
fs_parse API changes...
The following changes since commit f35aa2bc809eacc44c3cee41b52cef1c451d4a89:
tmpfs: switch to use of invalfc() (2020-02-07 14:48:44 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.vboxsf
for you to fetch changes up to 0fd169576648452725fa2949bf391d10883d3991:
fs: Add VirtualBox guest shared folder (vboxsf) support (2020-02-08 17:34:58 -0500)
----------------------------------------------------------------
Hans de Goede (1):
fs: Add VirtualBox guest shared folder (vboxsf) support
MAINTAINERS | 6 +
fs/Kconfig | 1 +
fs/Makefile | 1 +
fs/vboxsf/Kconfig | 10 +
fs/vboxsf/Makefile | 5 +
fs/vboxsf/dir.c | 427 +++++++++++++++++++++
fs/vboxsf/file.c | 379 +++++++++++++++++++
fs/vboxsf/shfl_hostintf.h | 901 ++++++++++++++++++++++++++++++++++++++++++++
fs/vboxsf/super.c | 491 ++++++++++++++++++++++++
fs/vboxsf/utils.c | 551 +++++++++++++++++++++++++++
fs/vboxsf/vboxsf_wrappers.c | 371 ++++++++++++++++++
fs/vboxsf/vfsmod.h | 137 +++++++
12 files changed, 3280 insertions(+)
create mode 100644 fs/vboxsf/Kconfig
create mode 100644 fs/vboxsf/Makefile
create mode 100644 fs/vboxsf/dir.c
create mode 100644 fs/vboxsf/file.c
create mode 100644 fs/vboxsf/shfl_hostintf.h
create mode 100644 fs/vboxsf/super.c
create mode 100644 fs/vboxsf/utils.c
create mode 100644 fs/vboxsf/vboxsf_wrappers.c
create mode 100644 fs/vboxsf/vfsmod.h
next reply other threads:[~2020-02-08 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 22:46 Al Viro [this message]
2020-02-09 21:30 ` [git pull] vboxsf 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=20200208224637.GH23230@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.