From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Kvasnica Subject: Re: vscsi 2TB patches Date: Tue, 4 Jan 2011 13:57:58 +0100 Message-ID: <4D231956.3080303@list.ims.co.at> References: <4D222D71.9020508@list.ims.co.at> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Return-path: In-Reply-To: <4D22FAD2020000780002A28C@vpn.id2.novell.com> References: <4D22FAD2020000780002A28C@vpn.id2.novell.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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 > Signed-off-by: Jun Kamada thanks ! How/where did you find it ? regards, Sam