From: Christoph Hellwig <hch@infradead.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
David Howells <dhowells@redhat.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: Merging virtualbox shared-folder VFS driver through drivers/staging?
Date: Sun, 11 Aug 2019 00:43:48 -0700 [thread overview]
Message-ID: <20190811074348.GA13485@infradead.org> (raw)
In-Reply-To: <20190811074005.GA4765@kroah.com>
On Sun, Aug 11, 2019 at 09:40:05AM +0200, Greg Kroah-Hartman wrote:
> > Since I do not see the lack of reviewing capacity problem get solved
> > anytime soon, I was wondering if you are ok with putting the code
> > in drivers/staging/vboxsf for now, until someone can review it and ack it
> > for moving over to sf/vboxsf ?
>
> I have no objection to that if the vfs developers do not mind.
We had really bad experiences with fs code in staging. I think it is
a bad idea that should not be repeated.
next prev parent reply other threads:[~2019-08-11 7:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 22:25 Merging virtualbox shared-folder VFS driver through drivers/staging? Hans de Goede
2019-08-11 0:50 ` Matthew Wilcox
2019-08-11 13:36 ` Hans de Goede
2019-08-11 7:40 ` Greg Kroah-Hartman
2019-08-11 7:43 ` Christoph Hellwig [this message]
2019-08-11 7:50 ` Greg Kroah-Hartman
2019-08-11 13:43 ` Hans de Goede
2019-08-11 13:49 ` Greg Kroah-Hartman
2019-08-12 11:22 ` Christoph Hellwig
2019-08-12 13:44 ` Gao Xiang
2019-08-11 9:00 ` Gao Xiang
2019-08-29 15:05 ` Hans de Goede
2019-08-30 16:43 ` Christoph Hellwig
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=20190811074348.GA13485@infradead.org \
--to=hch@infradead.org \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--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 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.