From: Chen Yu <yu.c.chen@intel.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Auke Kok <auke-jan.h.kok@intel.com>,
Jeff Garzik <jeff@garzik.org>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Len Brown <len.brown@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Shevchenko, Andriy" <andriy.shevchenko@intel.com>,
"Neftin, Sasha" <sasha.neftin@intel.com>,
"Lifshits, Vitaly" <vitaly.lifshits@intel.com>,
Chen Yu <yu.c.chen@intel.com>
Subject: [PATCH 0/2] Make WOL of e1000e consistent with sysfs device wakeup
Date: Fri, 22 May 2020 01:58:02 +0800 [thread overview]
Message-ID: <cover.1590081982.git.yu.c.chen@intel.com> (raw)
Currently the WOL(Wake On Lan) bahavior of e1000e is not consistent with its corresponding
device wake up ability.
Fix this by:
1. Do not wake up the system via WOL if device wakeup is disabled
2. Make WOL display info from ethtool consistent with device wake up
settings in sysfs
Chen Yu (2):
e1000e: Do not wake up the system via WOL if device wakeup is disabled
e1000e: Make WOL info in ethtool consistent with device wake up
ability
drivers/net/ethernet/intel/e1000e/ethtool.c | 2 +-
drivers/net/ethernet/intel/e1000e/netdev.c | 14 ++++++++++----
2 files changed, 11 insertions(+), 5 deletions(-)
--
2.17.1
next reply other threads:[~2020-05-21 17:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 17:58 Chen Yu [this message]
2020-05-21 17:59 ` [PATCH 1/2] e1000e: Do not wake up the system via WOL if device wakeup is disabled Chen Yu
2020-05-26 0:23 ` Sasha Levin
2020-05-26 3:34 ` Chen Yu
2020-06-15 18:51 ` Brown, Aaron F
2020-06-16 7:01 ` Chen Yu
2020-05-21 17:59 ` [PATCH 2/2] e1000e: Make WOL info in ethtool consistent with device wake up ability Chen Yu
2020-05-21 19:23 ` Michal Kubecek
2020-05-23 9:09 ` Chen Yu
2020-05-24 21:06 ` Michal Kubecek
2020-05-25 16:12 ` Chen Yu
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=cover.1590081982.git.yu.c.chen@intel.com \
--to=yu.c.chen@intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=auke-jan.h.kok@intel.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeff@garzik.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kuba@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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).