From: patchwork-bot+netdevbpf@kernel.org
To: Satish Kharat <satishkh@cisco.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v2 0/2] net:ethernet:enic: add VIC ids and link modes
Date: Wed, 25 Feb 2026 01:50:34 +0000 [thread overview]
Message-ID: <177198423428.31093.10138563715470068624.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260223-enic-cscwi36355-v2-0-63488194a974@cisco.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 23 Feb 2026 02:27:19 -0800 you wrote:
> Add VIC subsystem ids and their supported/advertised media types so ethtool
> reflects the hardware capabilities for the VIC variants.
>
> Signed-off-by: Satish Kharat <satishkh@cisco.com>
> ---
> Changes in v2:
> Addressed comments from Andrew Lunn
> - Removed the advertising of the link speed as we don't support autoneg.
> - Link to v1: https://lore.kernel.org/r/20260221-enic-cscwi36355-v1-0-5a01a6046d5e@cisco.com
>
> [...]
Here is the summary with links:
- [v2,1/2] net:ethernet:enic: add VIC subsystem ids
https://git.kernel.org/netdev/net-next/c/472e079f8c90
- [v2,2/2] net:ethernet:enic: map ethtool link modes by VIC type
https://git.kernel.org/netdev/net-next/c/426f1f5b8752
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:[~2026-02-25 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 10:27 [PATCH v2 0/2] net:ethernet:enic: add VIC ids and link modes Satish Kharat via B4 Relay
2026-02-23 10:27 ` [PATCH v2 1/2] net:ethernet:enic: add VIC subsystem ids Satish Kharat via B4 Relay
2026-02-23 10:27 ` [PATCH v2 2/2] net:ethernet:enic: map ethtool link modes by VIC type Satish Kharat via B4 Relay
2026-02-25 1:50 ` 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=177198423428.31093.10138563715470068624.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=satishkh@cisco.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