From: patchwork-bot+netdevbpf@kernel.org
To: Meng Tang <tangmeng@uniontech.com>
Cc: davem@davemloft.net, kuba@kernel.org, f.fainelli@gmail.com,
bcm-kernel-feedback-list@broadcom.com, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bcm63xx_enet: Use platform_get_irq() to get the interrupt
Date: Sat, 05 Mar 2022 05:40:12 +0000 [thread overview]
Message-ID: <164645881282.22557.2559177652719280936.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220303100815.25605-1-tangmeng@uniontech.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 3 Mar 2022 18:08:15 +0800 you wrote:
> platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on
> static allocation of IRQ resources in DT core code, this
> causes an issue when using hierarchical interrupt domains
> using "interrupts" property in the node as this bypassed
> the hierarchical setup and messed up the irq chaining.
>
> In preparation for removal of static setup of IRQ resource
> from DT core code use platform_get_irq().
>
> [...]
Here is the summary with links:
- bcm63xx_enet: Use platform_get_irq() to get the interrupt
https://git.kernel.org/netdev/net-next/c/43ff0d76f235
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-03-05 5:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 10:08 [PATCH] bcm63xx_enet: Use platform_get_irq() to get the interrupt Meng Tang
2022-03-05 5: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=164645881282.22557.2559177652719280936.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tangmeng@uniontech.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;
as well as URLs for NNTP newsgroup(s).