Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Kay Sievers <kay.sievers@vrfy.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: Sun, 25 Jan 2009 21:55:23 -0700	[thread overview]
Message-ID: <20090126045523.GB4376@colo.lackof.org> (raw)
In-Reply-To: <1232923996.2924.17.camel@nga>

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>

> 
> Cc: kyle@mcmartin.ca
> Cc: matthew@wil.cx
> Cc: linux-parisc@vger.kernel.org
> Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
> Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
> ---
>  drivers/parisc/dino.c |   11 ++++++-----
>  1 file changed, 6 insertions(+), 5 deletions(-)
> 
> --- a/drivers/parisc/dino.c
> +++ b/drivers/parisc/dino.c
> @@ -479,7 +479,7 @@ dino_card_setup(struct pci_bus *bus, voi
>  	res = &dino_dev->hba.lmmio_space;
>  	res->flags = IORESOURCE_MEM;
>  	size = scnprintf(name, sizeof(name), "Dino LMMIO (%s)", 
> -			 bus->bridge->bus_id);
> +			 dev_name(bus->bridge));
>  	res->name = kmalloc(size+1, GFP_KERNEL);
>  	if(res->name)
>  		strcpy((char *)res->name, name);
> @@ -493,7 +493,7 @@ dino_card_setup(struct pci_bus *bus, voi
>  		struct list_head *ln, *tmp_ln;
>  
>  		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.
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;
}

And that could mean anything.
The rest look fine.

thanks,
grant

>  		/* kill the bus, we can't do anything with it */
>  		list_for_each_safe(ln, tmp_ln, &bus->devices) {
>  			struct pci_dev *dev = pci_dev_b(ln);
> @@ -611,12 +611,12 @@ dino_fixup_bus(struct pci_bus *bus)
>  			}
>  					
>  			DBG("DEBUG %s assigning %d [0x%lx,0x%lx]\n",
> -			    bus->self->dev.bus_id, i,
> +			    dev_name(&bus->self->dev), i,
>  			    bus->self->resource[i].start,
>  			    bus->self->resource[i].end);
>  			pci_assign_resource(bus->self, i);
>  			DBG("DEBUG %s after assign %d [0x%lx,0x%lx]\n",
> -			    bus->self->dev.bus_id, i,
> +			    dev_name(&bus->self->dev), i,
>  			    bus->self->resource[i].start,
>  			    bus->self->resource[i].end);
>  		}
> @@ -1026,7 +1026,8 @@ static int __init dino_probe(struct pari
>  		dino_current_bus = bus->subordinate + 1;
>  		pci_bus_assign_resources(bus);
>  	} else {
> -		printk(KERN_ERR "ERROR: failed to scan PCI bus on %s (probably duplicate bus number %d)\n", dev->dev.bus_id, dino_current_bus);
> +		printk(KERN_ERR "ERROR: failed to scan PCI bus on %s (probably duplicate bus number %d)\n",
> +		       dev_name(&dev->dev), dino_current_bus);
>  		/* increment the bus number in case of duplicates */
>  		dino_current_bus++;
>  	}
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-01-26  4:55 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 [this message]
2009-01-26 12:27   ` Kay Sievers
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=20090126045523.GB4376@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=gregkh@suse.de \
    --cc=kay.sievers@vrfy.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