public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Lu Baolu <baolu.lu@linux.intel.com>,
	"Geyslan G. Bem" <geyslan@gmail.com>,
	peter.senna@gmail.com
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: host: iounmap before return
Date: Mon, 7 Dec 2015 14:37:24 +0300	[thread overview]
Message-ID: <56656F74.1020909@cogentembedded.com> (raw)
In-Reply-To: <566551CE.10604@linux.intel.com>

Hello.

On 12/07/2015 12:30 PM, Lu Baolu wrote:

>> This patch fixes a 'quirk_usb_handoff_xhci()' branch return that was not unmapping correctly.
>>
>> Coccinelle: scripts/coccinelle/free/iounmap.cocci
>>
>> Signed-off-by: Geyslan G. Bem <geyslan@gmail.com>
>> ---
>>   drivers/usb/host/pci-quirks.c | 3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/usb/host/pci-quirks.c b/drivers/usb/host/pci-quirks.c
>> index f940056..64150dd 100644
>> --- a/drivers/usb/host/pci-quirks.c
>> +++ b/drivers/usb/host/pci-quirks.c
>> @@ -990,7 +990,7 @@ static void quirk_usb_handoff_xhci(struct pci_dev *pdev)
>>   			/* We're reading garbage from the controller */
>>   			dev_warn(&pdev->dev,
>>   				 "xHCI controller failing to respond");
>> -			return;
>> +			goto out;
>
> If "out" is only used here, why not iounmap and return directly here?

    Why repeat the code? Nah, bad idea.

>>   		}
>>
>>   		if (!ext_cap_offset)
>> @@ -1062,6 +1062,7 @@ hc_init:
>>   			 XHCI_MAX_HALT_USEC, val);
>>   	}
>>
>> +out:
>>   	iounmap(base);
>>   }
>>

MBR, Sergei


  parent reply	other threads:[~2015-12-07 11:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-06 13:47 [PATCH] usb: host: iounmap before return Geyslan G. Bem
2015-12-07  9:30 ` Lu Baolu
2015-12-07 10:26   ` Geyslan G. Bem
2015-12-07 11:37   ` Sergei Shtylyov [this message]
2015-12-07 23:39     ` Geyslan G. Bem

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=56656F74.1020909@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=geyslan@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=peter.senna@gmail.com \
    /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