From: patchwork-bot+netdevbpf@kernel.org
To: Julien Panis <jpanis@baylibre.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, ast@kernel.org, daniel@iogearbox.net,
hawk@kernel.org, john.fastabend@gmail.com,
jacob.e.keller@intel.com, s-vadapalli@ti.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH net-next] net: ethernet: ti: am65-cpsw: Fix xdp_rxq error for disabled port
Date: Mon, 22 Apr 2024 08:20:47 +0000 [thread overview]
Message-ID: <171377404785.21182.10578807051583062281.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240418-am65-cpsw-am62a-crash-v1-1-81d710cbc11b@baylibre.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 18 Apr 2024 17:34:55 +0200 you wrote:
> When an ethX port is disabled in the device tree, an error is returned
> by xdp_rxq_info_reg() function while transitioning the CPSW device to
> the up state. The message 'Missing net_device from driver' is output.
>
> This patch fixes the issue by registering xdp_rxq info only if ethX
> port is enabled (i.e. ndev pointer is not NULL).
>
> [...]
Here is the summary with links:
- [net-next] net: ethernet: ti: am65-cpsw: Fix xdp_rxq error for disabled port
https://git.kernel.org/netdev/net-next/c/80b7aae9e3b8
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-22 8:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 15:34 [PATCH net-next] net: ethernet: ti: am65-cpsw: Fix xdp_rxq error for disabled port Julien Panis
2024-04-22 8:20 ` 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=171377404785.21182.10578807051583062281.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=john.fastabend@gmail.com \
--cc=jpanis@baylibre.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=s-vadapalli@ti.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.