From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Calvin Owens <calvin@wbinvd.org>
Cc: netdev@vger.kernel.org, Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jedrzej Jagielski <jedrzej.jagielski@intel.com>,
Ivan Vecera <ivecera@redhat.com>,
intel-wired-lan@lists.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH net] i40e: Prevent unwanted interface name changes
Date: Fri, 22 Aug 2025 08:31:51 +0200 [thread overview]
Message-ID: <0f19e779-ec78-419a-a261-c4550d778b45@molgen.mpg.de> (raw)
In-Reply-To: <94d7d5c0bb4fc171154ccff36e85261a9f186923.1755661118.git.calvin@wbinvd.org>
Dear Calvin,
Thank you for your patch..
Am 20.08.25 um 06:29 schrieb Calvin Owens:
> The same naming regression which was reported in ixgbe and fixed in
> commit e67a0bc3ed4f ("ixgbe: prevent from unwanted interface name
> changes") still exists in i40e.
>
> Fix i40e by setting the same flag, added in commit c5ec7f49b480
> ("devlink: let driver opt out of automatic phys_port_name generation").
>
> Fixes: 9e479d64dc58 ("i40e: Add initial devlink support")
> Signed-off-by: Calvin Owens <calvin@wbinvd.org>
> ---
> drivers/net/ethernet/intel/i40e/i40e_devlink.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/ethernet/intel/i40e/i40e_devlink.c b/drivers/net/ethernet/intel/i40e/i40e_devlink.c
> index cc4e9e2addb7..40f81e798151 100644
> --- a/drivers/net/ethernet/intel/i40e/i40e_devlink.c
> +++ b/drivers/net/ethernet/intel/i40e/i40e_devlink.c
> @@ -212,6 +212,7 @@ int i40e_devlink_create_port(struct i40e_pf *pf)
>
> attrs.flavour = DEVLINK_PORT_FLAVOUR_PHYSICAL;
> attrs.phys.port_number = pf->hw.pf_id;
> + attrs.no_phys_port_name = 1;
> i40e_devlink_set_switch_id(pf, &attrs.switch_id);
> devlink_port_attrs_set(&pf->devlink_port, &attrs);
> err = devlink_port_register(devlink, &pf->devlink_port, pf->hw.pf_id);
Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
Kind regards,
Paul
prev parent reply other threads:[~2025-08-22 6:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 4:29 [PATCH net] i40e: Prevent unwanted interface name changes Calvin Owens
2025-08-20 6:42 ` Michal Schmidt
2025-08-20 9:41 ` Przemek Kitszel
2025-08-20 16:11 ` Calvin Owens
2025-08-20 23:09 ` Calvin Owens
2025-08-20 15:31 ` Calvin Owens
2025-08-20 17:41 ` Calvin Owens
2025-08-21 8:00 ` Przemek Kitszel
2025-08-21 14:23 ` Calvin Owens
2025-08-21 20:39 ` Przemek Kitszel
2025-08-22 4:23 ` Calvin Owens
2025-08-22 6:30 ` [Intel-wired-lan] " Paul Menzel
2025-08-22 14:23 ` Jakub Kicinski
2025-08-22 20:25 ` [Intel-wired-lan] " Jacob Keller
2025-08-24 18:59 ` Calvin Owens
2025-08-20 15:51 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-08-20 23:16 ` Calvin Owens
2025-08-22 6:31 ` Paul Menzel [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=0f19e779-ec78-419a-a261-c4550d778b45@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=calvin@wbinvd.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=jedrzej.jagielski@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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).