All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: devel@driverdev.osuosl.org, vbox-dev@virtualbox.org,
	Michael Thayer <michael.thayer@oracle.com>,
	dri-devel@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] staging: vboxvideo: Add vboxvideo to drivers/staging
Date: Sat, 10 Jun 2017 18:50:18 +0200	[thread overview]
Message-ID: <20170610165018.GA11418@kroah.com> (raw)
In-Reply-To: <31d942c5-0659-8b3b-4c40-ac006f9d6fac@redhat.com>

On Sat, Jun 10, 2017 at 03:07:14PM +0200, Hans de Goede wrote:
> Hi,
> 
> On 09-06-17 11:58, 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.
> > 
> > At the same time we want to take our time to get this driver properly
> > cleaned up before submitting it as a normal driver under drivers/gpu/drm,
> > putting this driver in staging for now allows both.
> > 
> > Note this driver has already been significantly cleaned up, when I started
> > working on this the files under /usr/src/vboxguest/vboxvideo as installed
> > by Virtual Box 5.1.18 Guest Additions had a total linecount of 52681
> > lines. The version in this commit has 7275 lines.
> > 
> > Of those 7275 lines 3980 lines are in an osindependent directory which
> > contains portable code which is shared with other guest platforms such as
> > C-structure definitions for the virtual graphics card protocol and helper
> > functions for using these structures to communicate with the card. Since
> > these files are shared they are in the standard Virtual Box upstream code
> > style and not in the kernel coding style. All files outside of the
> > osindependent directory fully adhere to the kernel coding style.
> > 
> > Cc: vbox-dev@virtualbox.org
> > Cc: Michael Thayer <michael.thayer@oracle.com>
> > Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> > ---
> >   .config                                            |    1 +
> 
> <ugh> I just noticed that a .config changes have managed
> to get added to this patch, sorry.
> 
> Greg, lt me know if you want a new version if you can fix this
> up locally.

New version please!
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2017-06-10 16:50 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
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 [this message]

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=20170610165018.GA11418@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=daniel.vetter@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hdegoede@redhat.com \
    --cc=michael.thayer@oracle.com \
    --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.