Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758300Ab0KOUkw (ORCPT ); Mon, 15 Nov 2010 15:40:52 -0500 Received: from moutng.kundenserver.de ([212.227.17.10]:54961 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758263Ab0KOUkv (ORCPT ); Mon, 15 Nov 2010 15:40:51 -0500 Message-ID: <4CE19A94.8080504@vlnb.net> Date: Mon, 15 Nov 2010 23:39:48 +0300 From: Vladislav Bolkhovitin User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.10) Gecko/20100527 Thunderbird/3.0.5 MIME-Version: 1.0 To: Greg KH CC: Bart Van Assche , Dmitry Torokhov , Boaz Harrosh , linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, scst-devel , James Bottomley , Andrew Morton , FUJITA Tomonori , Mike Christie , Vu Pham , James Smart , Joe Eykholt , Andy Yan , Chetan Loke , Hannes Reinecke , Richard Sharpe , Daniel Henrique Debonzi Subject: Re: [PATCH 8/19]: SCST SYSFS interface implementation References: <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> <20101115184422.GA9566@kroah.com> In-Reply-To: <20101115184422.GA9566@kroah.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:v0oVPBjm7vdOyDopTl7qZhm+A25f0CTid838sVJ+Of7 rO6z5Uw94JPF0I8Lxpw8W18WasKtKGyH3w9rMFI4hEjGmR2Ntp VgZpCJBHZQOgvv7VFWdhIs1SmPrgrCg8b21rtmZr0Kp5mWx1nI maOtjCLz8tavvh+BV9vcnB5LZTPAKauh2/5+slBsxXcc8fegAN rGswHbMWdXNaZpWd3CnCg== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1624 Lines: 39 Greg KH, on 11/15/2010 09:44 PM wrote: > On Mon, Nov 15, 2010 at 06:45:24PM +0100, Bart Van Assche wrote: >> On Sun, Nov 14, 2010 at 12:59 AM, Greg KH wrote: >>> >>> On Sat, Nov 13, 2010 at 08:20:18PM +0300, Vladislav Bolkhovitin wrote: >>>> So, I decided to reimplement it to be completely synchronous. SYSFS >>>> authors did really great job and thanks to the excellent internal SYSFS >>>> design and implementation it is absolutely safe. See: >>>> >>>> [root@tgt ~]# modprobe scst >>>> [root@tgt ~]# cd /sys/kernel/scst_tgt/ >>> >>> Sorry, but no, you can't put this in /sys/kernel/ without getting the >>> approval of the sysfs maintainer. >>> >>> I really don't understand why you are using kobjects in the first place, >>> why isn't this in the main device tree in the kernel, using 'struct >>> device'? >> >> We might have missed something, but as far as we know it has not yet >> been explained in this thread why using 'struct device' would be an >> advantage over using 'struct kobject'. > > It's very simple. > > You want your device to show up in the global device tree in the kernel, > not off to one side, unconnected to anything else. > > Please use 'struct device', it is what you want to do here. But we don't have any device to show up in the global device tree! We don't have any devices in the struct device's understanding at all! Vlad -- 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/