Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264265AbTFPUdZ (ORCPT ); Mon, 16 Jun 2003 16:33:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264266AbTFPUdZ (ORCPT ); Mon, 16 Jun 2003 16:33:25 -0400 Received: from air-2.osdl.org ([65.172.181.6]:12764 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S264265AbTFPUdX (ORCPT ); Mon, 16 Jun 2003 16:33:23 -0400 Date: Mon, 16 Jun 2003 13:49:09 -0700 (PDT) From: Patrick Mochel X-X-Sender: mochel@cherise To: Alan Stern cc: Russell King , Greg KH , Subject: Re: Flaw in the driver-model implementation of attributes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1203 Lines: 30 > This doesn't provide any really good place to put device attributes that > are owned by the driver. They can't go in > /sysfs/class/pcmcia_socket/pcmcia_socket0/device/... > because the driver doesn't own the device. They can't go in > /sysfs/class/pcmcia_socket/pcmcia_socket0/driver/... > because they aren't attributes of the _driver_, they're attributes of the > _device_. And they certainly aren't class attributes. > > So where would you put them? You'd have to create another subdirectory of > /sysfs/class/pcmcia_socket/pcmcia_socket0/ > owned by the driver. No really good name for this subdirectory spings > to mind, and it's still kind of awkward. But doable. What is wrong with putting them in /sysfs/class/pcmcia_socket/pcmcia_socket0/ ? The driver owns that object. And, if it is device-specific feature, then it is likely related to what class the device belongs to, and is therefore relevant for that directory. -pat - 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/