All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	linux-pci@vger.kernel.org, linux-scsi@vger.kernel.org,
	Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH 4/5]pci:setup_bus.c Fix warning: variable 'retval' set but not used
Date: Fri, 18 Jun 2010 10:31:52 -0700	[thread overview]
Message-ID: <4C1BAD88.9050903@gmail.com> (raw)
In-Reply-To: <20100618102330.29eccb5b@virtuousgeek.org>

On 06/18/2010 10:23 AM, Jesse Barnes wrote:
> On Tue, 15 Jun 2010 22:33:53 -0700
> "Justin P. Mattock"<justinmattock@gmail.com>  wrote:
>
>> The below patch fixes a warning message when using gcc 4.6.0
>>    CC      drivers/pci/setup-bus.o
>> drivers/pci/setup-bus.c: In function 'pci_assign_unassigned_bridge_resources':
>> drivers/pci/setup-bus.c:868:6: warning: variable 'retval' set but not used
>>
>>   Signed-off-by: Justin P. Mattock<justinmattock@gmail.com>
>>
>> ---
>>   drivers/pci/setup-bus.c |    2 --
>>   1 files changed, 0 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
>> index 19b1113..215590b 100644
>> --- a/drivers/pci/setup-bus.c
>> +++ b/drivers/pci/setup-bus.c
>> @@ -865,7 +865,6 @@ void pci_assign_unassigned_bridge_resources(struct pci_dev *bridge)
>>   	struct pci_bus *parent = bridge->subordinate;
>>   	int tried_times = 0;
>>   	struct resource_list_x head, *list;
>> -	int retval;
>>   	unsigned long type_mask = IORESOURCE_IO | IORESOURCE_MEM |
>>   				  IORESOURCE_PREFETCH;
>>
>> @@ -874,7 +873,6 @@ void pci_assign_unassigned_bridge_resources(struct pci_dev *bridge)
>>   again:
>>   	pci_bus_size_bridges(parent);
>>   	__pci_bridge_assign_resources(bridge,&head);
>> -	retval = pci_reenable_device(bridge);
>>   	pci_set_master(bridge);
>>   	pci_enable_bridges(parent);
>>
>
> This has the same problem as your earlier bridge_enable patch; you need
> to keep the call to pci_reenable_device.  I should have caught this
> issue when Yinghai's patch went in: the right way to silence a warning
> about not checking a return value isn't to simply assign it to
> something, you really should *do* something as well, at least some
> debug output would be nice, but ideally handling the error in a sane
> way.
>


yeah I was still looking into the scsi patch with adding a printk
then I can look at this as well.

Justin P. Mattock

  reply	other threads:[~2010-06-18 17:31 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16  5:33 [PATCH 0/5] Fix set but unused variable warnings Justin P. Mattock
2010-06-16  5:33 ` [PATCH 1/5]wireless:hostap_main.c warning: variable 'iface' set but not used Justin P. Mattock
2010-06-16  5:33 ` [PATCH 2/5]wireless:hostap_ap.c Fix warning: variable 'fc' " Justin P. Mattock
     [not found] ` <1276666434-11227-1-git-send-email-justinmattock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-06-16  5:33   ` [PATCH 3/5]pci:bus.c Fix variable 'retval' " Justin P. Mattock
2010-06-16  5:33     ` Justin P. Mattock
2010-06-16  5:42     ` Julian Calaby
2010-06-16  5:42       ` Julian Calaby
2010-06-16  6:56       ` Justin P. Mattock
2010-06-16  6:07     ` Junchang Wang
2010-06-16  6:58       ` Justin P. Mattock
     [not found]       ` <20100616060738.GA12461-XdzxFlWC3YoNXa20cRcSYJWwCtiK4VeF@public.gmane.org>
2010-06-16 17:01         ` Justin P. Mattock
2010-06-16 17:01           ` Justin P. Mattock
2010-06-17 17:15       ` Justin P. Mattock
2010-06-16  5:33 ` [PATCH 4/5]pci:setup_bus.c Fix warning: " Justin P. Mattock
2010-06-18 17:23   ` Jesse Barnes
2010-06-18 17:31     ` Justin P. Mattock [this message]
2010-06-18 18:38     ` Justin P. Mattock
2010-06-18 18:48     ` Yinghai Lu
2010-06-18 19:49       ` Jesse Barnes
2010-06-18 19:59         ` Justin P. Mattock
     [not found]           ` <4C1BD024.1030707-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-06-18 20:05             ` Jesse Barnes
2010-06-18 20:05               ` Jesse Barnes
2010-06-18 20:26               ` Justin P. Mattock
2010-06-18 20:46                 ` Jesse Barnes
     [not found]                   ` <20100618134622.7db9f913-Y1mF5jBUw70BENJcbMCuUQ@public.gmane.org>
2010-06-18 21:12                     ` Justin P. Mattock
2010-06-18 21:12                       ` Justin P. Mattock
2010-06-16  5:33 ` [PATCH 5/5]scsi:hosts.c Fix warning: variable 'rval' " Justin P. Mattock
2010-06-16 11:05   ` Matthew Wilcox
2010-06-16 15:34   ` James Bottomley
2010-06-16 16:00     ` Justin P. Mattock
2010-06-16 17:25       ` Rolf Eike Beer
2010-06-16 17:33       ` James Bottomley
2010-06-16 18:14         ` Justin P. Mattock
     [not found]         ` <1276709590.2847.176.camel-0iu6Cu4xQGLYCGPCin2YbQ@public.gmane.org>
2010-06-17 16:16           ` Justin P. Mattock
2010-06-17 16:16             ` Justin P. Mattock
2010-06-18 19:37             ` James Bottomley
2010-06-18 19:55               ` Justin P. Mattock
2010-06-18 20:17               ` Justin P. Mattock
2010-06-16  5:52 ` [PATCH 0/5] Fix set but unused variable warnings Julian Calaby
2010-06-16  7:01   ` Justin P. Mattock
2010-06-16 11:09   ` Matthew Wilcox
2010-06-16 11:30     ` Julian Calaby

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=4C1BAD88.9050903@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yinghai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.