linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: dhowells@redhat.com, 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 10:13:35 +0100	[thread overview]
Message-ID: <25800.1277889215@redhat.com> (raw)
In-Reply-To: <4C2A6B6C.1000306@gmail.com>

Justin P. Mattock <justinmattock@gmail.com> wrote:

>  	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) {

That new if-statement still needs indenting one more tab stop.  It's indented
the same as the previous if-statement, but is actually in the body of that
previous if-statement.

The body of the second if-statement should be indented one tab beyond the if,
and else/else-if statements and the final closing brace should be indented
level with the if:

	if (...) {
		body;
	} else if (...) {
		body;
	} else {
		body;
	}

so that they line up vertically.

> +		dev_warn(dev, "dev:%p Failed to create firmware_node: %d\n",
> +			acpi_dev, fn);

The "dev:%p " seems like it ought to be superfluous if you're using
dev_warn(), and certainly, returning the pointer isn't really useful, I
suspect.

However, at this point you have two device struct pointers: dev and
&acip_dev->dev, so printing them both is may be good.  Perhaps something like:

+		dev_warn(&acpi_dev->dev,
+			 "Failed to create firmware_node link to %s %s: %d\n",
+			 dev_driver_string(dev), dev_name(dev), fn);

David

  parent reply	other threads:[~2010-06-30  9:13 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 [this message]
2010-06-30 13:21             ` Justin P. Mattock
2010-06-30 19:47             ` Justin P. Mattock
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=25800.1277889215@redhat.com \
    --to=dhowells@redhat.com \
    --cc=justinmattock@gmail.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).