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,
sasha.neftin@intel.com, vitaly.lifshits@intel.com
Subject: Re: [PATCH net 0/2][pull request] Intel Wired LAN Driver Updates 2022-02-01
Date: Wed, 02 Feb 2022 05:10:10 +0000 [thread overview]
Message-ID: <164377861057.30544.7924209825776669007.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220201173754.580305-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 Tue, 1 Feb 2022 09:37:52 -0800 you wrote:
> This series contains updates to e1000e driver only.
>
> Sasha removes CSME handshake with TGL platform as this is not supported
> and is causing hardware unit hangs to be reported.
>
> The following are changes since commit 881cc731df6af99a21622e9be25a23b81adcd10b:
> net: phy: Fix qca8081 with speeds lower than 2.5Gb/s
> and are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue 1GbE
>
> [...]
Here is the summary with links:
- [net,1/2] e1000e: Separate ADP board type from TGP
https://git.kernel.org/netdev/net/c/68defd528f94
- [net,2/2] e1000e: Handshake with CSME starts from ADL platforms
https://git.kernel.org/netdev/net/c/cad014b7b5a6
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:[~2022-02-02 5:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 17:37 [PATCH net 0/2][pull request] Intel Wired LAN Driver Updates 2022-02-01 Tony Nguyen
2022-02-01 17:37 ` [PATCH net 1/2] e1000e: Separate ADP board type from TGP Tony Nguyen
2022-02-01 17:37 ` [PATCH net 2/2] e1000e: Handshake with CSME starts from ADL platforms Tony Nguyen
2022-02-02 5:10 ` 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=164377861057.30544.7924209825776669007.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=sasha.neftin@intel.com \
--cc=vitaly.lifshits@intel.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).