From: Jakub Kicinski <kuba@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, sassmann@redhat.com,
kai.heng.feng@canonical.com, rjw@rjwysocki.net,
len.brown@intel.com, todd.e.brandt@intel.com,
sasha.neftin@intel.com, vitaly.lifshits@intel.com,
yu.c.chen@intel.com
Subject: Re: [PATCH net-next v2 0/2][pull request] 1GbE Intel Wired LAN Driver Updates 2021-03-15
Date: Tue, 16 Mar 2021 13:35:14 -0700 [thread overview]
Message-ID: <20210316133514.10b4fa2d@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20210316031659.3695692-1-anthony.l.nguyen@intel.com>
On Mon, 15 Mar 2021 20:16:57 -0700 Tony Nguyen wrote:
> 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.
>
> v2: remove __maybe_unused from e1000e_pm_prepare()
Thanks!
Acked-by: Jakub Kicinski <kuba@kernel.org>
next prev parent reply other threads:[~2021-03-16 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 3:16 [PATCH net-next v2 0/2][pull request] 1GbE Intel Wired LAN Driver Updates 2021-03-15 Tony Nguyen
2021-03-16 3:16 ` [PATCH net-next v2 1/2] e1000e: Leverage direct_complete to speed up s2ram Tony Nguyen
2021-03-16 3:16 ` [PATCH net-next v2 2/2] e1000e: Remove the runtime suspend restriction on CNP+ Tony Nguyen
2021-03-16 20:35 ` Jakub Kicinski [this message]
2021-03-16 22:10 ` [PATCH net-next v2 0/2][pull request] 1GbE Intel Wired LAN Driver Updates 2021-03-15 patchwork-bot+netdevbpf
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=20210316133514.10b4fa2d@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=kai.heng.feng@canonical.com \
--cc=len.brown@intel.com \
--cc=netdev@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sasha.neftin@intel.com \
--cc=sassmann@redhat.com \
--cc=todd.e.brandt@intel.com \
--cc=vitaly.lifshits@intel.com \
--cc=yu.c.chen@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 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.