From: Alex Elder <elder@ieee.org>
To: Heiner Kallweit <hkallweit1@gmail.com>,
Kang Minchul <tegongkang@gmail.com>,
Alex Elder <elder@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ipa: Remove redundant dev_err()
Date: Mon, 12 Dec 2022 07:11:27 -0600 [thread overview]
Message-ID: <3d13301c-c3fa-5a59-d4b6-cb45bf3fa18c@ieee.org> (raw)
In-Reply-To: <f04435d8-9af3-1fde-c2bf-fadd045b10a1@gmail.com>
On 12/11/22 10:34 AM, Heiner Kallweit wrote:
> On 11.12.2022 15:47, Kang Minchul wrote:
>> Function dev_err() is redundant because platform_get_irq_byname()
>> already prints an error.
>>
>> Signed-off-by: Kang Minchul <tegongkang@gmail.com>
>> ---
>> drivers/net/ipa/gsi.c | 5 +----
>> 1 file changed, 1 insertion(+), 4 deletions(-)
>>
>> diff --git a/drivers/net/ipa/gsi.c b/drivers/net/ipa/gsi.c
>> index 55226b264e3c..585cfd3f9ec0 100644
>> --- a/drivers/net/ipa/gsi.c
>> +++ b/drivers/net/ipa/gsi.c
>> @@ -1967,11 +1967,8 @@ int gsi_init(struct gsi *gsi, struct platform_device *pdev, bool prefetch,
>>
>> /* Get the GSI IRQ and request for it to wake the system */
>> ret = platform_get_irq_byname(pdev, "gsi");
>> - if (ret <= 0) {
>> - dev_err(gsi->dev,
>> - "DT error %d getting \"gsi\" IRQ property\n", ret);
>> + if (ret <= 0)
>
> According to the function description it can't return 0.
That's great! I explicitly checked for 0 because at the
time I couldn't *prove* that 0 was an invalid return, and
there was nothing obvious in the function saying so. I
*thought* it was invalid but lacked the guidance in the
code to know for sure.
Here is the commit that fixed that:
a85a6c86c25be driver core: platform: Clarify that IRQ 0 is invalid
And it turns out that this particular block of code got
moved but not modified after that comment commit:
0b8d676108451 net: ipa: request GSI IRQ later
Anyway, I'm very pleased this can be simplified.
-Alex
> You can further simplify the code.
> And you patch should be annotated net-next.
>
>> return ret ? : -EINVAL;
>> - }
>> irq = ret;
>>
>> ret = request_irq(irq, gsi_isr, 0, "gsi", gsi);
>
prev parent reply other threads:[~2022-12-12 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 14:47 Kang Minchul
2022-12-11 16:34 ` Heiner Kallweit
2022-12-12 7:19 ` Kang Minchul
2022-12-12 13:11 ` Alex Elder [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=3d13301c-c3fa-5a59-d4b6-cb45bf3fa18c@ieee.org \
--to=elder@ieee.org \
--cc=davem@davemloft.net \
--cc=elder@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tegongkang@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
all inboxes | Powered by JetHome®