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
Subject: Re: [PATCH net 0/4][pull request] Intel Wired LAN Driver Updates 2021-10-20
Date: Thu, 21 Oct 2021 11:20:08 +0000 [thread overview]
Message-ID: <163481520835.3134.9488542088302661465.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211020164957.3371484-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net.git (master)
by Tony Nguyen <anthony.l.nguyen@intel.com>:
On Wed, 20 Oct 2021 09:49:53 -0700 you wrote:
> This series contains updates to e1000e, igc, and ice drivers.
>
> Sasha fixes an issue with dropped packets on Tiger Lake platforms for
> e1000e and corrects a device ID for igc.
>
> Tony adds missing E810 device IDs for ice.
>
> [...]
Here is the summary with links:
- [net,1/4] e1000e: Separate TGP board type from SPT
https://git.kernel.org/netdev/net/c/280db5d42009
- [net,2/4] e1000e: Fix packet loss on Tiger Lake and later
https://git.kernel.org/netdev/net/c/639e298f432f
- [net,3/4] igc: Update I226_K device ID
https://git.kernel.org/netdev/net/c/79cc8322b6d8
- [net,4/4] ice: Add missing E810 device ids
https://git.kernel.org/netdev/net/c/7dcf78b870be
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-10-21 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 16:49 [PATCH net 0/4][pull request] Intel Wired LAN Driver Updates 2021-10-20 Tony Nguyen
2021-10-20 16:49 ` [PATCH net 1/4] e1000e: Separate TGP board type from SPT Tony Nguyen
2021-10-20 16:49 ` [PATCH net 2/4] e1000e: Fix packet loss on Tiger Lake and later Tony Nguyen
2021-10-20 16:49 ` [PATCH net 3/4] igc: Update I226_K device ID Tony Nguyen
2021-10-20 16:49 ` [PATCH net 4/4] ice: Add missing E810 device ids Tony Nguyen
2021-10-21 11:20 ` 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=163481520835.3134.9488542088302661465.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 \
/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.