From: Vincent Jardin <vjardin@free.fr>
To: netdev-bot+sashiko@kernel.org
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, ioana.ciornei@nxp.com,
vladimir.oltean@nxp.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] dpaa2-eth: DPNIs without a DPMAC should be virtual devlink ports
Date: Mon, 28 Sep 2026 13:33:05 +0200 [thread overview]
Message-ID: <arpQcc3pSDwiYKwE@L30177.local> (raw)
In-Reply-To: <179051507094.2160803.2316498936147241429@kernel.org>
Hi Mr Bot,
> [Severity: Medium]
> Can this race with the endpoint changed IRQ thread during probe?
Yes, see v2, patch 1/2.
> [Severity: Low]
> Is this still true when the topology changes after probe?
No, let's focus on the DPNIs for DPMAC.
> [Severity: Low]
> Is the warning that follows still accurate for a virtual port?
Yes, but with an edit based on Ioana's reviews.
pw-bot: cr
best regards,
Vincent
next prev parent reply other threads:[~2026-09-28 11:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 12:57 [PATCH net-next 0/2] dpaa2-eth: devlink port number from the DPMAC Vincent Jardin via B4 Relay
2026-09-23 12:58 ` [PATCH net-next 1/2] dpaa2-eth: use the DPMAC id as the devlink physical port number Vincent Jardin via B4 Relay
2026-09-27 13:17 ` netdev-bot+sashiko
2026-09-28 11:27 ` Vincent Jardin
2026-09-28 9:12 ` Ioana Ciornei
2026-09-28 11:29 ` Vincent Jardin
2026-09-23 12:58 ` [PATCH net-next 2/2] dpaa2-eth: DPNIs without a DPMAC should be virtual devlink ports Vincent Jardin via B4 Relay
2026-09-27 13:17 ` netdev-bot+sashiko
2026-09-28 11:33 ` Vincent Jardin [this message]
2026-09-28 9:18 ` Ioana Ciornei
2026-09-28 11:35 ` Vincent Jardin
2026-09-23 15:09 ` [PATCH net-next 0/2] dpaa2-eth: devlink port number from the DPMAC Ioana Ciornei
2026-09-24 11:58 ` Vincent Jardin
2026-09-28 12:31 ` Ioana Ciornei
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=arpQcc3pSDwiYKwE@L30177.local \
--to=vjardin@free.fr \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.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
all inboxes | Powered by JetHome®