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,
alexander.duyck@gmail.com, sasha.neftin@intel.com,
darcari@redhat.com, Yijun.Shen@dell.com, Perry.Yuan@dell.com,
anthony.wong@canonical.com, hdegoede@redhat.com,
mario.limonciello@dell.com
Subject: Re: [net 0/4][pull request] Intel Wired LAN Driver Updates 2020-12-23
Date: Mon, 28 Dec 2020 14:07:35 -0800 [thread overview]
Message-ID: <20201228140735.4949e592@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20201223233625.92519-1-anthony.l.nguyen@intel.com>
On Wed, 23 Dec 2020 15:36:21 -0800 Tony Nguyen wrote:
> Commit e086ba2fccda ("e1000e: disable s0ix entry and exit flows for ME
> systems") disabled S0ix flows for systems that have various incarnations of
> the i219-LM ethernet controller. This was done because of some regressions
> caused by an earlier commit 632fbd5eb5b0e ("e1000e: fix S0ix flows for
> cable connected case") with i219-LM controller.
>
> Per discussion with Intel architecture team this direction should be
> changed and allow S0ix flows to be used by default. This patch series
> includes directional changes for their conclusions in
> https://lkml.org/lkml/2020/12/13/15.
Pulled, thanks!
prev parent reply other threads:[~2020-12-28 23:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 23:36 [net 0/4][pull request] Intel Wired LAN Driver Updates 2020-12-23 Tony Nguyen
2020-12-23 23:36 ` [net 1/4] e1000e: Only run S0ix flows if shutdown succeeded Tony Nguyen
2020-12-23 23:36 ` [net 2/4] e1000e: bump up timeout to wait when ME un-configures ULP mode Tony Nguyen
2020-12-23 23:36 ` [net 3/4] Revert "e1000e: disable s0ix entry and exit flows for ME systems" Tony Nguyen
2020-12-23 23:36 ` [net 4/4] e1000e: Export S0ix flags to ethtool Tony Nguyen
2020-12-28 22:07 ` Jakub Kicinski [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=20201228140735.4949e592@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=Perry.Yuan@dell.com \
--cc=Yijun.Shen@dell.com \
--cc=alexander.duyck@gmail.com \
--cc=anthony.l.nguyen@intel.com \
--cc=anthony.wong@canonical.com \
--cc=darcari@redhat.com \
--cc=davem@davemloft.net \
--cc=hdegoede@redhat.com \
--cc=mario.limonciello@dell.com \
--cc=netdev@vger.kernel.org \
--cc=sasha.neftin@intel.com \
--cc=sassmann@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 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.