From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boaz Harrosh Subject: Re: [PATCH 8/19]: SCST SYSFS interface implementation Date: Mon, 15 Nov 2010 11:46:38 +0200 Message-ID: <4CE1017E.4090409@panasas.com> References: <20101022185437.GA9103@kroah.com> <4CD8566D.1020202@vlnb.net> <20101109002829.GA22633@kroah.com> <4CD9A9B8.70708@vlnb.net> <4CDA6CD4.3010308@panasas.com> <4CDAFE6E.7050200@vlnb.net> <4CDBBE80.40908@panasas.com> <4CDC56F9.9040601@vlnb.net> <20101112012315.GE17097@core.coreip.homeip.net> <4CDEC8D2.8080101@vlnb.net> <20101113235938.GA1827@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: Received: from natasha.panasas.com ([67.152.220.90]:44775 "EHLO natasha.panasas.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755000Ab0KOJsA (ORCPT ); Mon, 15 Nov 2010 04:48:00 -0500 In-Reply-To: <20101113235938.GA1827@kroah.com> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Greg KH Cc: Vladislav Bolkhovitin , Dmitry Torokhov , linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, scst-devel , James Bottomley , Andrew Morton , FUJITA Tomonori , Mike Christie , Vu Pham , Bart Van Assche , James Smart , Joe Eykholt , Andy Yan , Chetan Loke , Hannes Reinecke , Richard Sharpe , Daniel Henrique Debonzi On 11/14/2010 01:59 AM, Greg KH wrote: > In the end, I guess it really doesn't matter as this code isn't getting > merged so I shouldn't worry about it, right? > This is not nice and is uncharacteristic of you. This project, even though out-of-tree, is an old and mature project that has many users. These are all *Linux* users. The authors and community have come to us for help, and advice on making this code acceptable for mainline and hardening the code the way, only one project on the planet can do, the Linux community. I think it is our courtesy and obligation to the Linux users of this Project to comment where they are doing wrong and where they should do better. It is not of their choice to be out-of-tree. It is ours. The least we can do. Is give then some assistance if we can, and have 5 minutes of our time. All these issues we were discussing are interesting and are real Kernel problems. For instance the last comment you made was that for such a dynamic system and life time problems, and functionality. A better and expected solution might be the device tree and not sysfs. And for such big additions the sysfs maintainer must give his blessings. This is most valuable information regardless of if we accept their code or not at the end. (And we better explain ourselves well when we don't) > thanks, > > greg k-h Sincerely yours Boaz