lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAFLxGvx_p7NGMnRw9f-_KLF9H7jafHdP9CM7m0ADyVFWmV4oWw@mail.gmail.com>
Date:	Fri, 10 May 2013 07:38:36 +0200
From:	richard -rw- weinberger <richard.weinberger@...il.com>
To:	quickbooks office <quickbooks.office@...il.com>
Cc:	Josh Boyer <jwboyer@...il.com>,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	vbox-dev@...tualbox.org
Subject: Re: [PATCH] [SVN] Please Merge 7 VirtualBox Kernel Modules into the
 Linux Kernel

On Fri, May 10, 2013 at 5:40 AM, quickbooks office
<quickbooks.office@...il.com> wrote:
> On Wed, May 8, 2013 at 8:40 AM, Josh Boyer <jwboyer@...il.com> wrote:
>> On Wed, May 8, 2013 at 12:09 AM, quickbooks office
>> <quickbooks.office@...il.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
>
> Who are the appropriate maintainers for adding new (VirtualBox) kernel
> modules to the Linux kernel?
> And how would they go through proper review?

Please read:
Documentation/development-process/*
Documentation/SubmittingPatches

--
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ