All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@gmail.com>
To: quickbooks office <quickbooks.office@gmail.com>
Cc: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	vbox-dev@virtualbox.org
Subject: Re: [PATCH] [SVN] Please Merge 7 VirtualBox Kernel Modules into the Linux Kernel
Date: Wed, 8 May 2013 11:40:54 -0400	[thread overview]
Message-ID: <CA+5PVA5V59N7CaX++=059icOH1-u6a4U+B46LijMn0eeB1UZFw@mail.gmail.com> (raw)
In-Reply-To: <CACtbSuSDBe33DGfR0LFXCtzRYBaF-JuKBjYWu8QFEdw7nENPSA@mail.gmail.com>

On Wed, May 8, 2013 at 12:09 AM, quickbooks office
<quickbooks.office@gmail.com> wrote:
> Please Merge VirtualBox Kernel Modules into the Kernel.
>
> -----------------------------------------------------------------------------------------------------------
>
> svn co http://www.virtualbox.org/svn/vbox/trunk vbox
> sh '/home/user/vbox/src/VBox/Additions/linux/export_modules'
> VBoxGuestModules.tar.gz
>
> Extracting VBoxGuestModules.tar.gz will give the Source Code for 3
> modules (used in a Linux Guest):
>
> 1. vboxguest (VirtualBox guest kernel module)
>
> 2. vboxsf (VirtualBox guest kernel module for shared folders)
>
> 3. vboxvideo (VirtualBox guest kernel module for drm support)

That's not how this works.  The vbox developers need to submit them as
patches to the appropriate maintainers and they need to go through
proper review.  As far as I can tell, that hasn't been done because
they don't want to settle on a single API/ABI between the kernel and
userspace interfaces for vbox.

josh

  reply	other threads:[~2013-05-08 15:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08  4:09 [PATCH] [SVN] Please Merge 7 VirtualBox Kernel Modules into the Linux Kernel quickbooks office
2013-05-08 15:40 ` Josh Boyer [this message]
2013-05-10  3:40   ` quickbooks office
2013-05-10  5:38     ` richard -rw- weinberger

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='CA+5PVA5V59N7CaX++=059icOH1-u6a4U+B46LijMn0eeB1UZFw@mail.gmail.com' \
    --to=jwboyer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quickbooks.office@gmail.com \
    --cc=torvalds@linux-foundation.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.