From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Mon, 28 Feb 2005 19:56:43 +0000 Subject: Re: event sequencing Message-Id: <20050228195643.GC21508@kroah.com> List-Id: References: <9e473391050225081838f673c7@mail.gmail.com> In-Reply-To: <9e473391050225081838f673c7@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Mon, Feb 28, 2005 at 02:07:37PM -0500, Jon Smirl wrote: > On Mon, 28 Feb 2005 12:25:26 +0100, Kay Sievers wrote: > > It may work as a child of the physical device. Or something like: > > net/bridge/br_sysfs_if.c:br_sysfs_addif() > > I can make this work with a small pactch to drivers/base/class.c > I need to modify class_device_add to not stomp the parent field if it > is passed in. > > Greg, is this a reasonable way to fix this, or is a new API that > explicitly passes in the parent needed, or do you just hate the whole > idea in general? I like the idea of your patch, but I think it breaks when we remove the class_device device, right? Or if we remove the parent class_device first. thanks, greg k-h ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel