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, andrew+netdev@lunn.ch,
netdev@vger.kernel.org
Subject: Re: [PATCH net 0/8][pull request] Intel Wired LAN Driver Updates 2026-03-03 (ice, libie, iavf, igb, igc)
Date: Thu, 05 Mar 2026 02:40:29 +0000 [thread overview]
Message-ID: <177267842929.2487871.11008962542144563866.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260303231155.2895065-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 Tue, 3 Mar 2026 15:11:46 -0800 you wrote:
> Larysa removes VF restriction for LLDP filters on ice to allow for LLDP
> traffic to reach the correct destination.
>
> Jakub adds retry mechanism for AdminQ Read/Write SFF EEPROM call to
> follow hardware specification on ice.
>
> Zilin Guan adds cleanup path to free XDP rings on failure in
> ice_set_ringparam().
>
> [...]
Here is the summary with links:
- [net,1/8] ice: fix adding AQ LLDP filter for VF
https://git.kernel.org/netdev/net/c/eef33aa44935
- [net,2/8] ice: reintroduce retry mechanism for indirect AQ
https://git.kernel.org/netdev/net/c/326256c0a72d
- [net,3/8] ice: fix retry for AQ command 0x06EE
https://git.kernel.org/netdev/net/c/fb4903b3354a
- [net,4/8] ice: Fix memory leak in ice_set_ringparam()
https://git.kernel.org/netdev/net/c/fe868b499d16
- [net,5/8] libie: don't unroll if fwlog isn't supported
https://git.kernel.org/netdev/net/c/636cc3bd12f4
- [net,6/8] iavf: fix netdev->max_mtu to respect actual hardware limit
https://git.kernel.org/netdev/net/c/b84852170153
- [net,7/8] igb: Fix trigger of incorrect irq in igb_xsk_wakeup
https://git.kernel.org/netdev/net/c/d4c13ab36273
- [net,8/8] igc: Fix trigger of incorrect irq in igc_xsk_wakeup function
https://git.kernel.org/netdev/net/c/554a1c34c11a
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-03-05 2:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 23:11 [PATCH net 0/8][pull request] Intel Wired LAN Driver Updates 2026-03-03 (ice, libie, iavf, igb, igc) Tony Nguyen
2026-03-03 23:11 ` [PATCH net 1/8] ice: fix adding AQ LLDP filter for VF Tony Nguyen
2026-03-03 23:11 ` [PATCH net 2/8] ice: reintroduce retry mechanism for indirect AQ Tony Nguyen
2026-03-03 23:11 ` [PATCH net 3/8] ice: fix retry for AQ command 0x06EE Tony Nguyen
2026-03-05 23:24 ` Dawid Osuchowski
2026-03-05 23:55 ` Tony Nguyen
2026-03-03 23:11 ` [PATCH net 4/8] ice: Fix memory leak in ice_set_ringparam() Tony Nguyen
2026-03-03 23:11 ` [PATCH net 5/8] libie: don't unroll if fwlog isn't supported Tony Nguyen
2026-03-03 23:11 ` [PATCH net 6/8] iavf: fix netdev->max_mtu to respect actual hardware limit Tony Nguyen
2026-03-03 23:11 ` [PATCH net 7/8] igb: Fix trigger of incorrect irq in igb_xsk_wakeup Tony Nguyen
2026-03-03 23:11 ` [PATCH net 8/8] igc: Fix trigger of incorrect irq in igc_xsk_wakeup function Tony Nguyen
2026-03-05 2:40 ` 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=177267842929.2487871.11008962542144563866.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox