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
Subject: Re: [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2024-03-06 (igc, igb, ice)
Date: Fri, 08 Mar 2024 19:40:30 +0000 [thread overview]
Message-ID: <170992683082.9448.10703615335638966640.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240306182617.625932-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 Wed, 6 Mar 2024 10:26:11 -0800 you wrote:
> This series contains updates to igc, igb, and ice drivers.
>
> Vinicius removes double clearing of interrupt register which could cause
> timestamp events to be missed on igc and igb.
>
> Przemek corrects calculation of statistics which caused incorrect spikes
> in reporting for ice driver.
>
> [...]
Here is the summary with links:
- [net,1/3] igc: Fix missing time sync events
https://git.kernel.org/netdev/net/c/244ae992e3e8
- [net,2/3] igb: Fix missing time sync events
https://git.kernel.org/netdev/net/c/ee14cc9ea19b
- [net,3/3] ice: fix stats being updated by way too large values
https://git.kernel.org/netdev/net/c/257310e99870
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:[~2024-03-08 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 18:26 [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2024-03-06 (igc, igb, ice) Tony Nguyen
2024-03-06 18:26 ` [PATCH net 1/3] igc: Fix missing time sync events Tony Nguyen
2024-03-06 18:26 ` [PATCH net 2/3] igb: " Tony Nguyen
2024-03-06 18:26 ` [PATCH net 3/3] ice: fix stats being updated by way too large values Tony Nguyen
2024-03-08 19: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=170992683082.9448.10703615335638966640.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=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;
as well as URLs for NNTP newsgroup(s).