On Thu, 2007-11-29 at 21:20 +0100, Kay Sievers wrote:
quoted text > On Thu, 2007-11-29 at 15:09 -0500, Alan Stern wrote:
> > On Thu, 29 Nov 2007, Kay Sievers wrote:
quoted text > > > > There's another good reason for not assigning the name in
> > > > kobject_init(): Code that uses kobjects (like the driver core) doesn't
> > > > set the name until later.
> > >
> > > That can be done at any stage, I guess. We will rip out the name in the
> > > struct device anyway.
> >
> > Are you also going to change all the places in the kernel where the
> > device name (.bus_id) isn't set until after device_initialize() has
> > been called?
>
> Yes, I already have a patch that does that for all stuff that was needed
> on my boxes.
To be exact, bus_id will be removed from the device, and the device name
will be set and retrieved directly from the kobject.
Kay
-
unsubscribe notice 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/
Messages in current thread:
Re: [PATCH] kobject: make sure kobj->ktype is set before ... , Kay Sievers , (Thu Nov 29, 4:26 pm)