public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: acpi: struct device - replace bus_id with dev_name(), dev_set_name()
Date: Fri, 06 Feb 2009 22:48:06 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0902062248010.26256@localhost.localdomain> (raw)
In-Reply-To: <1232923256.2924.3.camel@nga>

applied
thanks,
--
Len Brown, Intel Open Source Technology Center

On Sun, 25 Jan 2009, Kay Sievers wrote:

> From: Kay Sievers <kay.sievers@vrfy.org>
> Subject: acpi: struct device - replace bus_id with dev_name(), dev_set_name()
> 
> Cc: lenb@kernel.org
> Cc: linux-acpi@vger.kernel.org
> Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
> Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
> 
> ---
>  drivers/acpi/glue.c |    8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> --- a/drivers/acpi/glue.c
> +++ b/drivers/acpi/glue.c
> @@ -255,12 +255,12 @@ static int acpi_platform_notify(struct d
>  	}
>  	type = acpi_get_bus_type(dev->bus);
>  	if (!type) {
> -		DBG("No ACPI bus support for %s\n", dev->bus_id);
> +		DBG("No ACPI bus support for %s\n", dev_name(dev));
>  		ret = -EINVAL;
>  		goto end;
>  	}
>  	if ((ret = type->find_device(dev, &handle)) != 0)
> -		DBG("Can't get handler for %s\n", dev->bus_id);
> +		DBG("Can't get handler for %s\n", dev_name(dev));
>        end:
>  	if (!ret)
>  		acpi_bind_one(dev, handle);
> @@ -271,10 +271,10 @@ static int acpi_platform_notify(struct d
>  
>  		acpi_get_name(dev->archdata.acpi_handle,
>  			      ACPI_FULL_PATHNAME, &buffer);
> -		DBG("Device %s -> %s\n", dev->bus_id, (char *)buffer.pointer);
> +		DBG("Device %s -> %s\n", dev_name(dev), (char *)buffer.pointer);
>  		kfree(buffer.pointer);
>  	} else
> -		DBG("Device %s -> No ACPI support\n", dev->bus_id);
> +		DBG("Device %s -> No ACPI support\n", dev_name(dev));
>  #endif
>  
>  	return ret;
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> From: Kay Sievers <kay.sievers@vrfy.org>
> Subject: acpi: struct device - replace bus_id with dev_name(), dev_set_name()
> 
> Cc: lenb@kernel.org
> Cc: linux-acpi@vger.kernel.org
> Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
> Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
> 
> ---
>  drivers/acpi/glue.c |    8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> --- a/drivers/acpi/glue.c
> +++ b/drivers/acpi/glue.c
> @@ -255,12 +255,12 @@ static int acpi_platform_notify(struct d
>  	}
>  	type = acpi_get_bus_type(dev->bus);
>  	if (!type) {
> -		DBG("No ACPI bus support for %s\n", dev->bus_id);
> +		DBG("No ACPI bus support for %s\n", dev_name(dev));
>  		ret = -EINVAL;
>  		goto end;
>  	}
>  	if ((ret = type->find_device(dev, &handle)) != 0)
> -		DBG("Can't get handler for %s\n", dev->bus_id);
> +		DBG("Can't get handler for %s\n", dev_name(dev));
>        end:
>  	if (!ret)
>  		acpi_bind_one(dev, handle);
> @@ -271,10 +271,10 @@ static int acpi_platform_notify(struct d
>  
>  		acpi_get_name(dev->archdata.acpi_handle,
>  			      ACPI_FULL_PATHNAME, &buffer);
> -		DBG("Device %s -> %s\n", dev->bus_id, (char *)buffer.pointer);
> +		DBG("Device %s -> %s\n", dev_name(dev), (char *)buffer.pointer);
>  		kfree(buffer.pointer);
>  	} else
> -		DBG("Device %s -> No ACPI support\n", dev->bus_id);
> +		DBG("Device %s -> No ACPI support\n", dev_name(dev));
>  #endif
>  
>  	return ret;
> 

      reply	other threads:[~2009-02-07  3:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-25 22:40 acpi: struct device - replace bus_id with dev_name(), dev_set_name() Kay Sievers
2009-02-07  3:48 ` Len Brown [this message]

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=alpine.LFD.2.00.0902062248010.26256@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=gregkh@suse.de \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-acpi@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