[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+5PVA615qJ+uJaHqCtYC45DF0E6A-wg+0_=xn2eCM-4O1-XVg@mail.gmail.com>
Date: Tue, 31 Jul 2012 08:48:38 -0400
From: Josh Boyer <jwboyer@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: "Andrew Stiegmann (stieg)" <astiegmann@...are.com>,
linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org, pv-drivers@...are.com,
vm-crosstalk@...are.com, cschamp@...are.com
Subject: Re: [vmw_vmci 00/11] VMCI for Linux
On Thu, Jul 26, 2012 at 9:46 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
> On Thu, Jul 26, 2012 at 09:06:25PM -0400, Josh Boyer wrote:
>> On Thu, Jul 26, 2012 at 7:39 PM, Andrew Stiegmann (stieg)
>> <astiegmann@...are.com> wrote:
>> > drivers/misc/Kconfig | 1 +
>> > drivers/misc/Makefile | 1 +
>> > drivers/misc/vmw_vmci/Kconfig | 16 +
>>
>> Is there a reason this isn't going into staging first? The Hyper-V
>> drivers went through staging and that actually seemed to work fairly
>> well.
>
> Is there some reason you feel this should be in the staging tree now?
> Why?
Apologies for the delayed reply. Was on vacation.
Mostly because this is only one of several drivers. One that the
other drivers depend on, and I don't see those posted at all. I'm
guessing we'll want changes that will cause those unposted drivers to
break. It just seems to make sense to work on the API in staging
rather than slam it into drivers/misc/.
josh
--
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