From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
sassmann@redhat.com
Subject: Re: [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2021-04-14
Date: Thu, 15 Apr 2021 21:40:09 +0000 [thread overview]
Message-ID: <161852280940.6246.10024726306502706869.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210414162032.3846384-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Wed, 14 Apr 2021 09:20:29 -0700 you wrote:
> This series contains updates to ixgbe and ice drivers.
>
> Alex Duyck fixes a NULL pointer dereference for ixgbe.
>
> Yongxin Liu fixes an unbalanced enable/disable which was causing a call
> trace with suspend for ixgbe.
>
> [...]
Here is the summary with links:
- [net,1/3] ixgbe: Fix NULL pointer dereference in ethtool loopback test
https://git.kernel.org/netdev/net/c/31166efb1cee
- [net,2/3] ixgbe: fix unbalanced device enable/disable in suspend/resume
https://git.kernel.org/netdev/net/c/debb9df31158
- [net,3/3] ice: Fix potential infinite loop when using u8 loop counter
https://git.kernel.org/netdev/net/c/ef963ae427aa
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:[~2021-04-15 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 16:20 [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2021-04-14 Tony Nguyen
2021-04-14 16:20 ` [PATCH net 1/3] ixgbe: Fix NULL pointer dereference in ethtool loopback test Tony Nguyen
2021-04-14 16:20 ` [PATCH net 2/3] ixgbe: fix unbalanced device enable/disable in suspend/resume Tony Nguyen
2021-04-14 16:20 ` [PATCH net 3/3] ice: Fix potential infinite loop when using u8 loop counter Tony Nguyen
2021-04-14 23:28 ` [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2021-04-14 Jakub Kicinski
2021-04-15 21: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=161852280940.6246.10024726306502706869.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sassmann@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.