From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: devel@driverdev.osuosl.org, vbox-dev@virtualbox.org,
David Airlie <airlied@linux.ie>,
Michael Thayer <michael.thayer@oracle.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Sean Paul <seanpaul@chromium.org>,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] staging: vboxvideo: Add vboxvideo to drivers/staging
Date: Fri, 9 Jun 2017 12:07:13 +0200 [thread overview]
Message-ID: <20170609100713.GB1405@kroah.com> (raw)
In-Reply-To: <20170609095831.24842-2-hdegoede@redhat.com>
On Fri, Jun 09, 2017 at 11:58:31AM +0200, Hans de Goede wrote:
> This commit adds the vboxvideo drm/kms driver for the virtual graphics
> card used in Virtual Box virtual machines to drivers/staging.
>
> Why drivers/staging? This driver is already being patched into the kernel
> by several distros, thus it is good to get this driver upstream soon, so
> that work on the driver can be easily shared.
Last time I looked, the user/kernel api was a horrid C++ structure mess,
and I couldn't tease apart the needed pieces to get everything to even
build properly. I'm glad to see this go in, but is that userspace api
going to stay solid? What happens when we find bugs (and odds are,
there are lots of them) with that api?
Can I get some signed-off-by from teh virtual box developers here that
they are ok with this work happening?
Oh, and thanks a lot for pushing for this, I appreciate it, it's just
that it seems too good to be true :)
thanks,
greg k-h
next prev parent reply other threads:[~2017-06-09 10:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 9:58 [PATCH 0/1] staging: vboxvideo: Add vboxvideo to drivers/staging Hans de Goede
2017-06-09 9:58 ` [PATCH] " Hans de Goede
2017-06-09 10:07 ` Greg Kroah-Hartman [this message]
2017-06-09 10:21 ` Hans de Goede
2017-06-09 10:40 ` Michael Thayer
2017-06-09 11:23 ` Hans de Goede
2017-06-09 12:33 ` Michael Thayer
2017-06-10 13:07 ` Hans de Goede
2017-06-10 16:50 ` 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=20170609100713.GB1405@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=jani.nikula@linux.intel.com \
--cc=michael.thayer@oracle.com \
--cc=seanpaul@chromium.org \
--cc=vbox-dev@virtualbox.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.