From: patchwork-bot+netdevbpf@kernel.org
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: claudiu.beznea.uj@bp.renesas.com, s.shtylyov@omp.ru,
paul.barker.ct@bp.renesas.com,
niklas.soderlund+renesas@ragnatech.se, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] net: ravb: Fix registered interrupt names
Date: Thu, 25 Apr 2024 15:40:30 +0000 [thread overview]
Message-ID: <171405963005.10966.1749832467271464576.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cde67b68adf115b3cf0b44c32334ae00b2fbb321.1713944647.git.geert+renesas@glider.be>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 24 Apr 2024 09:45:21 +0200 you wrote:
> As interrupts are now requested from ravb_probe(), before calling
> register_netdev(), ndev->name still contains the template "eth%d",
> leading to funny names in /proc/interrupts. E.g. on R-Car E3:
>
> 89: 0 0 GICv2 93 Level eth%d:ch22:multi
> 90: 0 3 GICv2 95 Level eth%d:ch24:emac
> 91: 0 23484 GICv2 71 Level eth%d:ch0:rx_be
> 92: 0 0 GICv2 72 Level eth%d:ch1:rx_nc
> 93: 0 13735 GICv2 89 Level eth%d:ch18:tx_be
> 94: 0 0 GICv2 90 Level eth%d:ch19:tx_nc
>
> [...]
Here is the summary with links:
- net: ravb: Fix registered interrupt names
https://git.kernel.org/netdev/net/c/0c81ea5a8e23
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:[~2024-04-25 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 7:45 [PATCH] net: ravb: Fix registered interrupt names Geert Uytterhoeven
2024-04-24 7:56 ` Niklas Söderlund
2024-04-24 9:10 ` Sergey Shtylyov
2024-04-24 9:19 ` Geert Uytterhoeven
2024-04-24 11:13 ` claudiu beznea
2024-04-24 22:45 ` Andrew Lunn
2024-04-25 14:16 ` Jakub Kicinski
2024-04-25 15: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=171405963005.10966.1749832467271464576.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=kuba@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=pabeni@redhat.com \
--cc=paul.barker.ct@bp.renesas.com \
--cc=s.shtylyov@omp.ru \
/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.