From: Valdis.Kletnieks@vt.edu
To: Josh Boyer <jwboyer@gmail.com>
Cc: Frank Mehnert <frank.mehnert@oracle.com>,
Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andy Hall <andy.hall@oracle.com>
Subject: Re: RFC: virtualbox tainting.
Date: Fri, 07 Oct 2011 12:22:26 -0400 [thread overview]
Message-ID: <14824.1318004546@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 07 Oct 2011 11:16:13 EDT." <CA+5PVA4v0D_ppnjN_k_6AcDEfH_U0Nn9WLfb3J84JGBGBOFBsg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
On Fri, 07 Oct 2011 11:16:13 EDT, Josh Boyer said:
> In all seriousness, is there a reason these modules haven't been
> submitted to the staging tree? Perhaps this was attempted in the past
> and I'm just not finding references to it.
I haven't actually checked what the churn rate of the kernel side of VirtualBox is, but
there *is* some benefit if you have a package that includes both userspace and kernel
code, to keep them in sync.
Currently, VirtualBox is at 4.1.4. Now, if they decide they need to change/fix/extend
the API for some reason, they can just ship a 4.1.6 and be happy. If the code is
in-tree, then they are basically stuck with the API - they can't ship a 4.1.6 that can
get away with assuming that all the kernel API is there. So you have to carry around
workarounds and test-for-features code and all that stuff.
I don't know - maybe the Oracle crew think the API is stable enough now that they can
afford to do that. But Frank would probably be the one to speak to how in/out of tree
would affect their development/support methodology.
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-10-07 16:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 19:05 Dave Jones
2011-10-06 19:44 ` Greg KH
2011-10-06 19:50 ` Dave Jones
2011-10-06 19:53 ` Valdis.Kletnieks
2011-10-06 20:03 ` Dave Jones
2011-10-06 20:06 ` Greg KH
2011-10-06 19:58 ` Greg KH
2011-10-06 20:04 ` Dave Jones
2011-10-06 20:30 ` Greg KH
2011-10-07 8:01 ` Jiri Kosina
2011-10-07 10:02 ` Alan Cox
2011-10-07 16:04 ` Valdis.Kletnieks
2011-10-07 17:01 ` Greg KH
2011-10-07 17:46 ` Dave Jones
2011-10-07 7:03 ` Bastian Blank
2011-10-07 14:40 ` Frank Mehnert
2011-10-07 15:10 ` Dave Jones
2011-10-09 20:12 ` Frank Mehnert
2011-10-07 15:16 ` Josh Boyer
2011-10-07 16:22 ` Valdis.Kletnieks [this message]
2011-10-07 18:10 ` Josh Boyer
2011-10-07 18:33 ` Valdis.Kletnieks
2011-10-10 7:58 ` Pekka Enberg
2011-10-10 8:25 ` Dave Airlie
2011-10-10 14:24 ` Greg KH
2011-10-10 16:35 ` Pekka Enberg
2011-10-10 16:49 ` Dave Airlie
2011-10-10 16:51 ` Pekka Enberg
2011-10-10 8:41 ` Maarten Lankhorst
2011-10-10 11:42 ` Josh Boyer
2011-10-12 0:57 ` Parag Warudkar
2011-10-12 7:55 ` Alex Riesen
2011-10-12 14:08 ` Parag Warudkar
2011-10-12 14:18 ` Alex Riesen
2011-10-12 15:00 ` Parag Warudkar
2011-10-12 19:55 ` Zan Lynx
2011-10-12 20:54 ` Parag Warudkar
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=14824.1318004546@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=andy.hall@oracle.com \
--cc=davej@redhat.com \
--cc=frank.mehnert@oracle.com \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®