From: David Yang Date: Thu, 11 Jun 2026 07:08:47 +0000 (+0800) Subject: net: dsa: dsa_loop: avoid devlink resource IDs collision with PARENT_TOP X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=b2772157e5ae458112441dd7ac895440e090611f;p=thirdparty%2Flinux.git net: dsa: dsa_loop: avoid devlink resource IDs collision with PARENT_TOP This might not cause real problems, but the dsa_loop devlink resource ID collides with the sentinel DEVLINK_RESOURCE_ID_PARENT_TOP (0). Avoid it by keeping the real resource IDs starting at 1. Signed-off-by: David Yang Link: https://patch.msgid.link/20260611070856.889700-2-mmyangfl@gmail.com Signed-off-by: Jakub Kicinski --- diff --git a/drivers/net/dsa/dsa_loop.c b/drivers/net/dsa/dsa_loop.c index 7058faf23592b..0e35e9841b9b2 100644 --- a/drivers/net/dsa/dsa_loop.c +++ b/drivers/net/dsa/dsa_loop.c @@ -75,6 +75,7 @@ static struct phy_device *phydevs[PHY_MAX_ADDR]; static struct mdio_device *switch_mdiodev; enum dsa_loop_devlink_resource_id { + DSA_LOOP_DEVLINK_PARAM_ID_NONE, /* DEVLINK_RESOURCE_ID_PARENT_TOP */ DSA_LOOP_DEVLINK_PARAM_ID_VTU, };