From: Kay Sievers <kay.sievers@vrfy.org>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Greg KH <greg@kroah.com>, Magnus Damm <damm@opensource.se>,
linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] driver core: Early dev_name() support.
Date: Mon, 15 Mar 2010 12:29:23 +0100 [thread overview]
Message-ID: <ac3eb2511003150429u5aa2e6c8w9ecfcc77293dd82b@mail.gmail.com> (raw)
In-Reply-To: <20100315080359.GA15171@linux-sh.org>
On Mon, Mar 15, 2010 at 09:03, Paul Mundt <lethal@linux-sh.org> wrote:
> On Thu, Mar 11, 2010 at 08:59:18PM +0100, Kay Sievers wrote:
>> > ??static inline const char *dev_name(const struct device *dev)
>> > ??{
>> > + ?? ?? ?? /* Use the init name until the kobject becomes available */
>>
>> This should probably state that it's used for getting names out of
>> unregistered devices. Otherwise it sounds confusing.
>>
> It's not clear that that distinction makes things any less confusing.
> Early devices are registered, they just haven't been fully initialized
> yet.
For the driver core, "registered" devices are devices where
device_add() or device_register() has been called. Initialized devices
are devices which device_initialize() was called for. The devices you
mean are not "registered" in that sense, right?
Thanks,
Kay
next prev parent reply other threads:[~2010-03-15 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 6:57 [PATCH] driver core: Early dev_name() support Paul Mundt
2010-03-10 2:37 ` Greg KH
2010-03-10 3:21 ` Paul Mundt
2010-03-10 3:28 ` Greg KH
2010-03-10 4:10 ` Paul Mundt
2010-03-11 19:59 ` Kay Sievers
2010-03-15 8:03 ` Paul Mundt
2010-03-15 11:29 ` Kay Sievers [this message]
2010-03-15 11:56 ` Paul Mundt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ac3eb2511003150429u5aa2e6c8w9ecfcc77293dd82b@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=damm@opensource.se \
--cc=greg@kroah.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).