From: Christoph Hellwig <hch@infradead.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Michael Thayer <michael.thayer@oracle.com>,
"Knut St . Osmundsen" <knut.osmundsen@oracle.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC v2 1/2] virt: Add vboxguest driver for Virtual Box Guest integration
Date: Fri, 25 Aug 2017 08:19:19 -0700 [thread overview]
Message-ID: <20170825151919.GA16108@infradead.org> (raw)
In-Reply-To: <64a29ce3-3e48-5ce8-64a0-c4384cdd5a94@redhat.com>
On Fri, Aug 25, 2017 at 05:13:35PM +0200, Hans de Goede wrote:
> You know I've been working on this for almost 2 fulltime months
I don't, and I don't care to be honest. Figuring out what do
do about the userspace API/ABI should be your first priority,
and you should have discussed this on the linux-api list where
I didn't see anything about this driver.
We have a general stance to fix userspace APIs/ABIs before inclusion,
and in the few cases where we did it turned into a giant trainwreck.
The prime example is the Android binder, which has been a giant mess.
And that's something a lot more important than a weird hobbyist
hypersvior.
next prev parent reply other threads:[~2017-08-25 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 14:37 [RFC v2 0/2] Add Virtual Box vboxguest and vboxsf guest drivers to the mainline kernel Hans de Goede
2017-08-25 14:37 ` [RFC v2 1/2] virt: Add vboxguest driver for Virtual Box Guest integration Hans de Goede
2017-08-25 14:58 ` Christoph Hellwig
2017-08-25 15:00 ` Hans de Goede
2017-08-25 15:03 ` Christoph Hellwig
2017-08-25 15:06 ` Hans de Goede
2017-08-25 15:09 ` Christoph Hellwig
2017-08-25 15:13 ` Hans de Goede
2017-08-25 15:19 ` Christoph Hellwig [this message]
2017-08-25 14:37 ` [RFC v2 2/2] fs: Add VirtualBox guest shared folder (vboxsf) support Hans de Goede
2017-08-25 15:02 ` 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=20170825151919.GA16108@infradead.org \
--to=hch@infradead.org \
--cc=Larry.Finger@lwfinger.net \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=knut.osmundsen@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.thayer@oracle.com \
/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).