From: Dongliang Mu <dzm91@hust.edu.cn>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>, lihuya <lihuya@hust.edu.cn>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"hust-os-kernel-patches@googlegroups.com"
<hust-os-kernel-patches@googlegroups.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] usb: dwc3: remove dead code in dwc3_otg_get_irq
Date: Tue, 25 Apr 2023 07:29:55 +0800 [thread overview]
Message-ID: <ead628fe-c7fc-5e1e-0eba-02683a21b429@hust.edu.cn> (raw)
In-Reply-To: <20230424213339.avocjfchjd2ptaqg@synopsys.com>
On 2023/4/25 05:33, 'Thinh Nguyen' via HUST OS Kernel Contribution wrote:
> On Mon, Apr 24, 2023, lihuya wrote:
>> platform_get_irq() only return non-zero irq number on success, or
>> negative error number on failure.
>>
>> There is no need to check the return value of platform_get_irq()
>> to determine the return value of dwc3_otg_get_irq(), removing
>> them to solve this problem.
>>
>> Signed-off-by: lihuya <lihuya@hust.edu.cn>
> Is this your full name?
Hi Yuhang,
Please use your full name: Yuhang Liang. This is essential in the kernel
patch submission.
Dongliang Mu
>
>> ---
>> drivers/usb/dwc3/drd.c | 5 -----
>> 1 file changed, 5 deletions(-)
>>
>> diff --git a/drivers/usb/dwc3/drd.c b/drivers/usb/dwc3/drd.c
>> index 039bf241769a..c2e09700212d 100644
>> --- a/drivers/usb/dwc3/drd.c
>> +++ b/drivers/usb/dwc3/drd.c
>> @@ -154,11 +154,6 @@ static int dwc3_otg_get_irq(struct dwc3 *dwc)
>> goto out;
>>
>> irq = platform_get_irq(dwc3_pdev, 0);
>> - if (irq > 0)
>> - goto out;
>> -
>> - if (!irq)
>> - irq = -EINVAL;
>>
>> out:
>> return irq;
>> --
>> 2.34.1
>>
> FWIW, here's the ack again.
>
> Acked-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
>
> Thanks,
> Thinh
>
next prev parent reply other threads:[~2023-04-24 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 10:59 [PATCH RESEND] usb: dwc3: remove dead code in dwc3_otg_get_irq lihuya
2023-04-24 21:33 ` Thinh Nguyen
2023-04-24 23:29 ` Dongliang Mu [this message]
2023-04-25 8:57 ` Sergey Shtylyov
2023-04-25 9:10 ` Dongliang Mu
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=ead628fe-c7fc-5e1e-0eba-02683a21b429@hust.edu.cn \
--to=dzm91@hust.edu.cn \
--cc=Thinh.Nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=lihuya@hust.edu.cn \
--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