From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: devel@driverdev.osuosl.org, David Howells <dhowells@redhat.com>,
Hans de Goede <hdegoede@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v17 0/1] staging: Add VirtualBox guest shared folder (vboxsf) support
Date: Mon, 28 Oct 2019 12:41:59 +0100 [thread overview]
Message-ID: <20191028114159.GA6961@kroah.com> (raw)
In-Reply-To: <20191028113950.GA2406@infradead.org>
On Mon, Oct 28, 2019 at 04:39:50AM -0700, Christoph Hellwig wrote:
> On Mon, Oct 28, 2019 at 12:17:43PM +0100, Hans de Goede wrote:
> > Hi Greg,
> >
> > As discussed previously can you please take vboxsf upstream through
> > drivers/staging?
> >
> > It has seen many revisions on the fsdevel list, but it seems that the
> > fsdevel people are to busy to pick it up.
> >
> > Previous versions of this patch have been reviewed by Al Viro, David Howells
> > and Christoph Hellwig (all in the Cc) and I believe that the current
> > version addresses all their review remarks.
>
> Please just send it to Linus directly. This is the equivalent of
> consumer hardware enablement and it is in a state as clean as it gets
> for the rather messed up protocol.
I can add it to my patches to go to Linus for 5.4-final if you don't
object to it going into drivers/staging/
thanks,
greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2019-10-28 12:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 11:17 [PATCH v17 0/1] staging: Add VirtualBox guest shared folder (vboxsf) support Hans de Goede
2019-10-28 11:17 ` [PATCH v17] " Hans de Goede
2019-10-28 11:39 ` [PATCH v17 0/1] " Christoph Hellwig
2019-10-28 11:41 ` Greg Kroah-Hartman [this message]
2019-11-01 9:12 ` Greg Kroah-Hartman
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=20191028114159.GA6961@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=hdegoede@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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).