From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org, ivecera@redhat.com,
jiri@nvidia.com
Subject: Re: [PATCH net 0/2][pull request] Intel Wired LAN Driver Updates 2023-11-06 (i40e)
Date: Thu, 09 Nov 2023 02:50:31 +0000 [thread overview]
Message-ID: <169949823122.3016.13007722711516370248.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231107003600.653796-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net.git (main)
by Tony Nguyen <anthony.l.nguyen@intel.com>:
On Mon, 6 Nov 2023 16:35:57 -0800 you wrote:
> This series contains updates to i40e driver only.
>
> Ivan Vecera resolves a couple issues with devlink; removing a call to
> devlink_port_type_clear() and ensuring devlink port is unregistered
> after the net device.
>
> The following are changes since commit c1ed833e0b3b7b9edc82b97b73b2a8a10ceab241:
> Merge branch 'smc-fixes'
> and are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue 40GbE
>
> [...]
Here is the summary with links:
- [net,1/2] i40e: Do not call devlink_port_type_clear()
https://git.kernel.org/netdev/net/c/e96fe283c6f4
- [net,2/2] i40e: Fix devlink port unregistering
https://git.kernel.org/netdev/net/c/aa54d846f361
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:[~2023-11-09 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 0:35 [PATCH net 0/2][pull request] Intel Wired LAN Driver Updates 2023-11-06 (i40e) Tony Nguyen
2023-11-07 0:35 ` [PATCH net 1/2] i40e: Do not call devlink_port_type_clear() Tony Nguyen
2023-11-07 0:35 ` [PATCH net 2/2] i40e: Fix devlink port unregistering Tony Nguyen
2023-11-09 2: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=169949823122.3016.13007722711516370248.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ivecera@redhat.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.