From: patchwork-bot+netdevbpf@kernel.org
To: Li Qiong <liqiong@nfschina.com>
Cc: horatiu.vultur@microchip.com, UNGLinuxDriver@microchip.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, yuzhe@nfschina.com,
renyu@nfschina.com, jiaming@nfschina.com,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] net: lan966x: fix checking for return value of platform_get_irq_byname()
Date: Fri, 12 Aug 2022 10:40:13 +0000 [thread overview]
Message-ID: <166030081397.15777.15613376655712609091.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220812030954.24050-1-liqiong@nfschina.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 12 Aug 2022 11:09:54 +0800 you wrote:
> The platform_get_irq_byname() returns non-zero IRQ number
> or negative error number. "if (irq)" always true, chang it
> to "if (irq > 0)"
>
> Signed-off-by: Li Qiong <liqiong@nfschina.com>
> ---
> drivers/net/ethernet/microchip/lan966x/lan966x_main.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Here is the summary with links:
- net: lan966x: fix checking for return value of platform_get_irq_byname()
https://git.kernel.org/netdev/net/c/40b4ac880e21
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-08-12 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 3:09 [PATCH] net: lan966x: fix checking for return value of platform_get_irq_byname() Li Qiong
2022-08-12 10:40 ` patchwork-bot+netdevbpf [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=166030081397.15777.15613376655712609091.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=jiaming@nfschina.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liqiong@nfschina.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=renyu@nfschina.com \
--cc=yuzhe@nfschina.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 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.