linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	lenb@kernel.org
Subject: Re: [PATCH 3/5]acpi:glue.c Fix warning: variable 'ret' set but not used
Date: Wed, 30 Jun 2010 12:47:21 -0700	[thread overview]
Message-ID: <4C2B9F49.8090304@gmail.com> (raw)
In-Reply-To: <25800.1277889215@redhat.com>

o.k. hopefully this is getting close to being right.. I ended up 
spending the later half of the morning looking for 
dev_driver_string(dev) until I read device.h and realized you actually 
use that it's self to gather the debug info etc..(I admit it, I'm a newbie!)

anyways here is the updated patch, let me know if something need a 
changing..


 From 16df81551d1899e650ae28ea8d41931f7c391c7a Mon Sep 17 00:00:00 2001
From: Justin P. Mattock <justinmattock@gmail.com>
Date: Wed, 30 Jun 2010 12:34:32 -0700
Subject: [PATCH]acpi:glue.c Fix Fix warning: variable 'ret' set but not used

Fix a warning message generated by gcc:
Im getting a warning message when building with gcc 4.6.0
   CC      drivers/acpi/glue.o
drivers/acpi/glue.c: In function 'acpi_bind_one':
drivers/acpi/glue.c:163:7: warning: variable 'ret' set but not used

  Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
  Signed-off-by: David Howells <dhowells@redhat.com>
---
  drivers/acpi/glue.c |   16 +++++++++++++---
  1 files changed, 13 insertions(+), 3 deletions(-)

diff --git a/drivers/acpi/glue.c b/drivers/acpi/glue.c
index 4af6301..11ad510 100644
--- a/drivers/acpi/glue.c
+++ b/drivers/acpi/glue.c
@@ -145,6 +145,7 @@ static int acpi_bind_one(struct device *dev, 
acpi_handle handle)
  {
  	struct acpi_device *acpi_dev;
  	acpi_status status;
+	int fn, pn;

  	if (dev->archdata.acpi_handle) {
  		dev_warn(dev, "Drivers changed 'acpi_handle'\n");
@@ -160,12 +161,21 @@ static int acpi_bind_one(struct device *dev, 
acpi_handle handle)

  	status = acpi_bus_get_device(handle, &acpi_dev);
  	if (!ACPI_FAILURE(status)) {
-		int ret;

-		ret = sysfs_create_link(&dev->kobj, &acpi_dev->dev.kobj,
+		fn = sysfs_create_link(&dev->kobj, &acpi_dev->dev.kobj,
  				"firmware_node");
-		ret = sysfs_create_link(&acpi_dev->dev.kobj, &dev->kobj,
+		pn = sysfs_create_link(&acpi_dev->dev.kobj, &dev->kobj,
  				"physical_node");
+		if (fn) {
+			dev_warn(&acpi_dev->dev,
+				"Failed to create firmware_node link to %s %s: %d\n",
+				dev_driver_string(dev), dev_name(dev), fn);
+		} else if (pn) {
+			dev_warn(&acpi_dev->dev,
+				"Failed to create physical_node link to %s %s: %d\n",
+				dev_driver_string(dev), dev_name(dev), pn);
+				return AE_ERROR;
+		}			
  		if (acpi_dev->wakeup.flags.valid) {
  			device_set_wakeup_capable(dev, true);
  			device_set_wakeup_enable(dev,
-- 
1.7.1.rc1.21.gf3bd6


cheers,

Justin P. Mattock

  parent reply	other threads:[~2010-06-30 19:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C28E14D.5050701@gmail.com>
     [not found] ` <1277621246-10960-4-git-send-email-justinmattock@gmail.com>
     [not found]   ` <1277621246-10960-1-git-send-email-justinmattock@gmail.com>
     [not found]     ` <7214.1277729293@redhat.com>
     [not found]       ` <8066.1277750854@redhat.com>
2010-06-29  3:23         ` [PATCH 3/5]acpi:glue.c Fix warning: variable 'ret' set but not used Justin P. Mattock
2010-06-29 15:47         ` David Howells
2010-06-29 17:14           ` Justin P. Mattock
2010-06-29 21:53           ` Justin P. Mattock
2010-06-30  9:13           ` David Howells
2010-06-30 13:21             ` Justin P. Mattock
2010-06-30 19:47             ` Justin P. Mattock [this message]
2010-07-01  9:31             ` David Howells
2010-07-01 13:41               ` Justin P. Mattock
2010-07-01 20:01               ` Justin P. Mattock
2010-07-02  0:10               ` David Howells
2010-07-02  0:59                 ` Justin P. Mattock

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=4C2B9F49.8090304@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@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).