lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <168078901880.17216.8863252682451924859.git-patchwork-notify@kernel.org> Date: Thu, 06 Apr 2023 13:50:18 +0000 From: patchwork-bot+netdevbpf@...nel.org To: Louis Peens <louis.peens@...igine.com> Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com, leonro@...dia.com, simon.horman@...igine.com, netdev@...r.kernel.org, oss-drivers@...igine.com Subject: Re: [PATCH net-next v2] nfp: initialize netdev's dev_port with correct id Hello: This patch was applied to netdev/net-next.git (main) by Paolo Abeni <pabeni@...hat.com>: On Wed, 5 Apr 2023 14:08:29 +0200 you wrote: > From: Yinjun Zhang <yinjun.zhang@...igine.com> > > `dev_port` is used to differentiate devices that instantiate from > the same function, which is the case in most of NFP NICs. > > In some customized scenario, `dev_port` is used to rename netdev > instead of `phys_port_name`. Example rules using `dev_port`: > > [...] Here is the summary with links: - [net-next,v2] nfp: initialize netdev's dev_port with correct id https://git.kernel.org/netdev/net-next/c/0ebd4fd6b906 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists