This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] vscsi 2TB patches

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] vscsi 2TB patches
From: Samuel Kvasnica <bugreports@xxxxxxxxxxxxxx>
Date: Tue, 4 Jan 2011 13:57:58 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 04 Jan 2011 04:53:19 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D22FAD2020000780002A28C@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IMS AG
References: <4D222D71.9020508@xxxxxxxxxxxxxx>
References: <4D22FAD2020000780002A28C@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
On 01/04/2011 10:47 AM, Jan Beulich wrote:
>> Could please somebody here take care to add this to mainstream code ?
>> SuSE people were not interested really and the original author is not
> Sort of interesting a statement - iirc we responded that we'd take
> the changes once someone knowing the code reviewed them, and
> suggested that you post them here (which now you did, but you'll
> need to at least one more time to get thing into proper shape as
> pointed out by Pasi).
Well, so lets say, suse was at least something like "reluctant" to
accept the code.
I mean, I invested 90% of effort needed to identify, report, fix & test
this bug.

Given the fact, I don't submit kernel patches on daily basis, I would
have welcomed
somebody who does this regularly and actually maintains the code to take
care of the rest.

You might call it lazy or sloppy approach, but its all about efficiency.
Subscribing just
another mailing list, searching for the infos, submission standards etc.
is just
much more work on my side than actually fixing the issue.
> Signed-off-by: Tomonari Horikoshi <t.horikoshi@xxxxxxxxxxxxxx>
> Signed-off-by: Jun Kamada <kama@xxxxxxxxxxxxxx>
thanks ! How/where did you find it ?



Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>