From: Yuehaibing <yuehaibing@huawei.com>
To: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: dwc2: Fix unused label warning
Date: Mon, 2 Nov 2020 16:39:55 +0800 [thread overview]
Message-ID: <2aa957ab-d31d-f22f-e470-19169220e6a9@huawei.com> (raw)
In-Reply-To: <d3249c9c-e937-7ba1-e21b-3c89a79cb184@synopsys.com>
On 2020/11/2 15:04, Minas Harutyunyan wrote:
> On 10/31/2020 10:03 AM, YueHaibing wrote:
>> drivers/usb/dwc2/platform.c: In function ‘dwc2_driver_probe’:
>> drivers/usb/dwc2/platform.c:611:1: warning: label ‘error_debugfs’ defined but not used [-Wunused-label]
>> error_debugfs:
>> ^~~~~~~~~~~~~
>>
>> Move label 'error_debugfs' to ifdef block.
>>
>> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
>> ---
>> drivers/usb/dwc2/platform.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/usb/dwc2/platform.c b/drivers/usb/dwc2/platform.c
>> index e2820676beb1..5f18acac7406 100644
>> --- a/drivers/usb/dwc2/platform.c
>> +++ b/drivers/usb/dwc2/platform.c
>> @@ -608,10 +608,13 @@ static int dwc2_driver_probe(struct platform_device *dev)
>> #endif /* CONFIG_USB_DWC2_PERIPHERAL || CONFIG_USB_DWC2_DUAL_ROLE */
>> return 0;
>>
>> +#if IS_ENABLED(CONFIG_USB_DWC2_PERIPHERAL) || \
>> + IS_ENABLED(CONFIG_USB_DWC2_DUAL_ROLE)
>> error_debugfs:
>> dwc2_debugfs_exit(hsotg);
>> if (hsotg->hcd_enabled)
>> dwc2_hcd_remove(hsotg);
>> +#endif
>> error_drd:
>> dwc2_drd_exit(hsotg);
>>
>>
> Thank you for patch. Identical patch submitted by on 10/17/2020 by
> Martin Blumenstingl: [PATCH] usb: dwc2: Avoid leaving the error_debugfs
> label unused. I'm already ACKed it.
Thanks for this info.
> Thanks,
> Minas
>
prev parent reply other threads:[~2020-11-02 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 6:03 YueHaibing
2020-11-02 7:04 ` Minas Harutyunyan
2020-11-02 8:39 ` Yuehaibing [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=2aa957ab-d31d-f22f-e470-19169220e6a9@huawei.com \
--to=yuehaibing@huawei.com \
--cc=Minas.Harutyunyan@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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
all inboxes | Powered by JetHome®