[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071130103032.6393d846@gondolin.boeblingen.de.ibm.com>
Date: Fri, 30 Nov 2007 10:30:32 +0100
From: Cornelia Huck <cornelia.huck@...ibm.com>
To: Kay Sievers <kay.sievers@...y.org>
Cc: Alan Stern <stern@...land.harvard.edu>, Greg KH <greg@...ah.com>,
Kernel development list <linux-kernel@...r.kernel.org>,
Jonathan Corbet <corbet@....net>,
Randy Dunlap <randy.dunlap@...cle.com>
Subject: Re: [PATCH] kobject: make sure kobj->ktype is set before
kobject_init
On Thu, 29 Nov 2007 21:26:40 +0100,
Kay Sievers <kay.sievers@...y.org> wrote:
> On Thu, 2007-11-29 at 21:20 +0100, Kay Sievers wrote:
> > On Thu, 2007-11-29 at 15:09 -0500, Alan Stern wrote:
> > > On Thu, 29 Nov 2007, Kay Sievers wrote:
>
> > > > > 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?
Hmpf, ccw does this as well...
> >
> > 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.
I guess you'll have accessor functions for the bus id for use by higher
level code?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists