[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <161593260813.31300.14807554720705655276.git-patchwork-notify@kernel.org>
Date: Tue, 16 Mar 2021 22:10:08 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Tony Nguyen <anthony.l.nguyen@...el.com>
Cc: davem@...emloft.net, kuba@...nel.org, netdev@...r.kernel.org,
sassmann@...hat.com, kai.heng.feng@...onical.com,
rjw@...ysocki.net, len.brown@...el.com, todd.e.brandt@...el.com,
sasha.neftin@...el.com, vitaly.lifshits@...el.com,
yu.c.chen@...el.com
Subject: Re: [PATCH net-next v2 0/2][pull request] 1GbE Intel Wired LAN Driver
Updates 2021-03-15
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Mon, 15 Mar 2021 20:16:57 -0700 you wrote:
> This series contains updates to e1000e only.
>
> Chen Yu says:
>
> The NIC is put in runtime suspend status when there is no cable connected.
> As a result, it is safe to keep non-wakeup NIC in runtime suspended during
> s2ram because the system does not rely on the NIC plug event nor WoL to
> wake up the system. Besides that, unlike the s2idle, s2ram does not need to
> manipulate S0ix settings during suspend.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] e1000e: Leverage direct_complete to speed up s2ram
https://git.kernel.org/netdev/net-next/c/ccf8b940e5fd
- [net-next,v2,2/2] e1000e: Remove the runtime suspend restriction on CNP+
https://git.kernel.org/netdev/net-next/c/3335369bad99
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists