From: Kay Sievers <kay.sievers@vrfy.org>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: kyle@mcmartin.ca, matthew@wil.cx, linux-parisc@vger.kernel.org,
gregkh <gregkh@suse.de>
Subject: Re: parisc: struct device - replace bus_id with dev_name(), dev_set_name()
Date: Mon, 26 Jan 2009 13:27:48 +0100 [thread overview]
Message-ID: <ac3eb2510901260427p5f2bbeedv57368043a88dd1f4@mail.gmail.com> (raw)
In-Reply-To: <20090126045523.GB4376@colo.lackof.org>
On Mon, Jan 26, 2009 at 05:55, Grant Grundler <grundler@parisc-linux.org> wrote:
> On Sun, Jan 25, 2009 at 11:53:16PM +0100, Kay Sievers wrote:
>> From: Kay Sievers <kay.sievers@vrfy.org>
>> Subject: parisc: struct device - replace bus_id with dev_name(), dev_set_name()
>
> In general, no objection. Just one nit below.
>
> Otherwise, please add:
> Reviewed-by: Grant Grundler <grundler@parisc-linux.org>
>> printk(KERN_ERR "Dino: cannot attach bus %s\n",
>> - bus->bridge->bus_id);
>> + dev_name(bus->bridge));
>
> I think the "cannot attach bus" string needs to be changed to
> "cannot attach dev" or whatever dev_name() is supposed to represent.
The code probably uses a "struct device" to represent a "bus", which
sounds fine because the "devices" are more "objects" than "devices"
sometimes.
> While the code in include/linux/device.h is using "bus_id",
> the comments say:
>
> static inline const char *dev_name(const struct device *dev)
> {
> /* will be changed into kobject_name(&dev->kobj) in the near future */
> return dev->bus_id;
> }
It's the "name" of a "device", the comment has already gone away with
the final patch in the bus_id series.
Thanks,
Kay
next prev parent reply other threads:[~2009-01-26 12:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 22:53 parisc: struct device - replace bus_id with dev_name(), dev_set_name() Kay Sievers
2009-01-26 4:55 ` Grant Grundler
2009-01-26 12:27 ` Kay Sievers [this message]
2009-01-26 17:39 ` Greg KH
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=ac3eb2510901260427p5f2bbeedv57368043a88dd1f4@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=gregkh@suse.de \
--cc=grundler@parisc-linux.org \
--cc=kyle@mcmartin.ca \
--cc=linux-parisc@vger.kernel.org \
--cc=matthew@wil.cx \
/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).