From: patchwork-bot+netdevbpf@kernel.org
To: Bui Duc Phuc <phucduc.bui@gmail.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, wens@kernel.org,
jernej.skrabec@gmail.com, samuel@sholland.org, linusw@kernel.org,
kees@kernel.org, bartosz.golaszewski@oss.qualcomm.com,
arnd@arndb.de, sr@denx.de, mripard@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net] net: ethernet: sun4i-emac: Fix IRQ error handling
Date: Thu, 27 Aug 2026 08:10:06 +0000 [thread overview]
Message-ID: <178781820640.1094636.14217098118734046137.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260824100901.31675-1-phucduc.bui@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 24 Aug 2026 17:09:01 +0700 you wrote:
> From: bui duc phuc <phucduc.bui@gmail.com>
>
> irq_of_parse_and_map() returns 0 when parsing or mapping an IRQ fails.
> The current code checks for -ENXIO and therefore does not detect the
> failure.
>
> Check for a zero return value and convert it to -ENXIO.
>
> [...]
Here is the summary with links:
- [net] net: ethernet: sun4i-emac: Fix IRQ error handling
https://git.kernel.org/netdev/net/c/991c2be78257
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:[~2026-08-27 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 10:09 [PATCH net] net: ethernet: sun4i-emac: Fix IRQ error handling phucduc.bui
2026-08-25 10:09 ` sashiko-bot
2026-08-25 10:55 ` Bui Duc Phuc
2026-08-25 10:32 ` Andre Przywara
2026-08-25 10:44 ` Bui Duc Phuc
2026-08-27 8:10 ` 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=178781820640.1094636.14217098118734046137.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=arnd@arndb.de \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jernej.skrabec@gmail.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phucduc.bui@gmail.com \
--cc=samuel@sholland.org \
--cc=sr@denx.de \
--cc=wens@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 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.