[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AA84436.3050205@codemonkey.ws>
Date: Wed, 09 Sep 2009 19:11:34 -0500
From: Anthony Liguori <anthony@...emonkey.ws>
To: Jeremy Fitzhardinge <jeremy@...p.org>
CC: Christoph Hellwig <hch@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"pv-drivers@...are.com" <pv-drivers@...are.com>,
LKML <linux-kernel@...r.kernel.org>,
virtualization <virtualization@...ts.linux-foundation.org>,
"Chetan.Loke@...lex.Com" <Chetan.Loke@...lex.Com>,
James Bottomley <James.Bottomley@...e.de>, akataria@...are.com,
Rolf Eike Beer <eike-kernel@...tec.de>
Subject: Re: [PATCH] SCSI driver for VMware's virtual HBA - V4.
Jeremy Fitzhardinge wrote:
> On 09/09/09 16:34, Anthony Liguori wrote:
>
>> We haven't even been successful in getting the Xen folks to present
>> their work on lkml before shipping it to their users. Why would we
>> expect more from VMware if we're willing to merge the Xen stuff?
>>
>>
>
> The Xen code may be out of tree, but it has always been readily
> available from a well-known place. I don't think its comparable.
>
Once an ABI is set in stone, there's very little that can be done on
lkml to review the ABI in any serious way.
VMware has repeatedly done this in the past. Ship a product with their
own drivers, then submit something to lkml saying that the ABI cannot be
changed because it's present in a shipping product.
I'll admit, Xen hasn't been as bad as VMware in this regard, but it's
certainly not perfect either.
Regards,
Anthony Liguori
> J
>
--
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