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/3][pull request] Intel Wired LAN Driver Updates 2025-07-15 (ixgbe, fm10k, i40e, ice)
Date: Thu, 17 Jul 2025 00:00:09 +0000 [thread overview]
Message-ID: <175271040926.1368016.3485291934007397973.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250715202948.3841437-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, 15 Jul 2025 13:29:43 -0700 you wrote:
> Arnd Bergmann resolves compile issues with large NR_CPUS for ixgbe, fm10k,
> and i40e.
>
> For ice:
> Dave adds a NULL check for LAG netdev.
>
> Michal corrects a pointer check in debugfs initialization.
>
> [...]
Here is the summary with links:
- [net,1/3] ethernet: intel: fix building with large NR_CPUS
https://git.kernel.org/netdev/net/c/24171a5a4a95
- [net,2/3] ice: add NULL check in eswitch lag check
https://git.kernel.org/netdev/net/c/3ce58b01ada4
- [net,3/3] ice: check correct pointer in fwlog debugfs
https://git.kernel.org/netdev/net/c/bedd0330a19b
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:[~2025-07-16 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 20:29 [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2025-07-15 (ixgbe, fm10k, i40e, ice) Tony Nguyen
2025-07-15 20:29 ` [PATCH net 1/3] ethernet: intel: fix building with large NR_CPUS Tony Nguyen
2025-07-15 20:29 ` [PATCH net 2/3] ice: add NULL check in eswitch lag check Tony Nguyen
2025-07-15 20:29 ` [PATCH net 3/3] ice: check correct pointer in fwlog debugfs Tony Nguyen
2025-07-17 0:00 ` 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=175271040926.1368016.3485291934007397973.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 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.