Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Nelson@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
	Shannon <shannon.nelson@amd.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	edumazet@google.com, pabeni@redhat.com, andrew+netdev@lunn.ch,
	jacob.e.keller@intel.com, brett.creeley@amd.com
Subject: Re: [PATCH net-next 0/5] ionic: minor code updates
Date: Thu, 12 Dec 2024 11:20:31 +0000	[thread overview]
Message-ID: <173400243150.2263704.13209593856094716019.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241210183045.67878-1-shannon.nelson@amd.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Tue, 10 Dec 2024 10:30:40 -0800 you wrote:
> These are a few updates to the ionic driver, mostly for handling
> newer/faster QSFP connectors.
> 
> Brett Creeley (2):
>   ionic: Use VLAN_ETH_HLEN when possible
>   ionic: Translate IONIC_RC_ENOSUPP to EOPNOTSUPP
> 
> [...]

Here is the summary with links:
  - [net-next,1/5] ionic: add asic codes to firmware interface file
    https://git.kernel.org/netdev/net-next/c/4aa567b1df8b
  - [net-next,2/5] ionic: Use VLAN_ETH_HLEN when possible
    https://git.kernel.org/netdev/net-next/c/33ce1d41c133
  - [net-next,3/5] ionic: Translate IONIC_RC_ENOSUPP to EOPNOTSUPP
    https://git.kernel.org/netdev/net-next/c/7c372bac12b2
  - [net-next,4/5] ionic: add speed defines for 200G and 400G
    https://git.kernel.org/netdev/net-next/c/a8b05dd3389f
  - [net-next,5/5] ionic: add support for QSFP_PLUS_CMIS
    https://git.kernel.org/netdev/net-next/c/a857c841e7ea

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-12-12 11:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10 18:30 [PATCH net-next 0/5] ionic: minor code updates Shannon Nelson
2024-12-10 18:30 ` [PATCH net-next 1/5] ionic: add asic codes to firmware interface file Shannon Nelson
2024-12-10 22:44   ` Jacob Keller
2024-12-11  3:36   ` Kalesh Anakkur Purayil
2024-12-10 18:30 ` [PATCH net-next 2/5] ionic: Use VLAN_ETH_HLEN when possible Shannon Nelson
2024-12-10 22:45   ` Jacob Keller
2024-12-11  3:32   ` Kalesh Anakkur Purayil
2024-12-10 18:30 ` [PATCH net-next 3/5] ionic: Translate IONIC_RC_ENOSUPP to EOPNOTSUPP Shannon Nelson
2024-12-10 22:45   ` Jacob Keller
2024-12-11  3:31   ` Kalesh Anakkur Purayil
2024-12-10 18:30 ` [PATCH net-next 4/5] ionic: add speed defines for 200G and 400G Shannon Nelson
2024-12-10 22:53   ` Jacob Keller
2024-12-10 23:21     ` Nelson, Shannon
2024-12-10 18:30 ` [PATCH net-next 5/5] ionic: add support for QSFP_PLUS_CMIS Shannon Nelson
2024-12-10 22:53   ` Jacob Keller
2024-12-11  3:30   ` Kalesh Anakkur Purayil
2024-12-11 10:12   ` Ido Schimmel
2024-12-11 17:15     ` Nelson, Shannon
2024-12-12 11:20 ` 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=173400243150.2263704.13209593856094716019.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Nelson@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=brett.creeley@amd.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jacob.e.keller@intel.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shannon.nelson@amd.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