Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756928Ab0DVAJY (ORCPT ); Wed, 21 Apr 2010 20:09:24 -0400 Received: from smtp-outbound-2.vmware.com ([65.115.85.73]:52230 "EHLO smtp-outbound-2.vmware.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755516Ab0DVAJV (ORCPT ); Wed, 21 Apr 2010 20:09:21 -0400 Date: Wed, 21 Apr 2010 17:09:19 -0700 From: Dmitry Torokhov To: Andrew Morton Cc: "linux-kernel@vger.kernel.org" , "pv-drivers@vmware.com" , Avi Kivity , Jeremy Fitzhardinge Subject: Re: [PATCH v2] VMware Balloon driver Message-ID: <20100422000919.GC4021@dtor-ws.eng.vmware.com> References: <20100404215202.GA13020@dtor-ws.eng.vmware.com> <20100405142419.2c9bea3d.akpm@linux-foundation.org> <20100415210030.GA5359@dtor-ws.eng.vmware.com> <20100421195935.GA972@dtor-ws.eng.vmware.com> <20100421131836.8b31a8c6.akpm@linux-foundation.org> <20100421205208.GA4021@dtor-ws.eng.vmware.com> <20100421141325.e2832455.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100421141325.e2832455.akpm@linux-foundation.org> User-Agent: Mutt/1.5.20 (2009-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1514 Lines: 43 On Wed, Apr 21, 2010 at 02:13:25PM -0700, Andrew Morton wrote: > On Wed, 21 Apr 2010 13:52:08 -0700 > Dmitry Torokhov wrote: > > > On Wed, Apr 21, 2010 at 01:18:36PM -0700, Andrew Morton wrote: > > > On Wed, 21 Apr 2010 12:59:35 -0700 > > > Dmitry Torokhov wrote: > > > > > > > Do you see any issues with the driver? > > > > > > Only my near-complete cluelessness on the whole topic. > > > > > > > Will you be the one picking it > > > > up and queueing for mainline? > > > > > > Spose so. > > > > Good. I don't suppose we have a chance making into .34? Being a > > completely new driver and all... > > It's foggy. Is there a good-sounding reason for pushing it in this > late? > We want to get the driver accepted in distributions so that users do not have to deal with an out-of-tree module and many distributions have "upstream first" requirement. The driver has been shipping for a number of years and users running on VMware platform will have it installed as part of VMware Tools even if it will not come from a distribution, thus there should not be additional risk in pulling the driver into mainline. The driver will only activate if host is VMware so everyone else should not be affected at all. Thanks, Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/