From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: yu.c.chen@intel.com, Stable@vger.kernel.org,
aaron.f.brown@intel.com, andriy.shevchenko@linux.intel.com,
jeffrey.t.kirsher@intel.com, rafael.j.wysocki@intel.com
Subject: Re: FAILED: patch "[PATCH] e1000e: Do not wake up the system via WOL if device wakeup is" failed to apply to 4.9-stable tree
Date: Tue, 23 Jun 2020 09:53:42 -0400 [thread overview]
Message-ID: <20200623135342.GZ1931@sasha-vm> (raw)
In-Reply-To: <15929135091516@kroah.com>
On Tue, Jun 23, 2020 at 01:58:29PM +0200, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.9-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 6bf6be1127f7e6d4bf39f84d56854e944d045d74 Mon Sep 17 00:00:00 2001
>From: Chen Yu <yu.c.chen@intel.com>
>Date: Fri, 22 May 2020 01:59:00 +0800
>Subject: [PATCH] e1000e: Do not wake up the system via WOL if device wakeup is
> disabled
>
>Currently the system will be woken up via WOL(Wake On LAN) even if the
>device wakeup ability has been disabled via sysfs:
> cat /sys/devices/pci0000:00/0000:00:1f.6/power/wakeup
> disabled
>
>The system should not be woken up if the user has explicitly
>disabled the wake up ability for this device.
>
>This patch clears the WOL ability of this network device if the
>user has disabled the wake up ability in sysfs.
>
>Fixes: bc7f75fa9788 ("[E1000E]: New pci-express e1000 driver")
>Reported-by: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
>Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>Cc: <Stable@vger.kernel.org>
>Signed-off-by: Chen Yu <yu.c.chen@intel.com>
>Tested-by: Aaron Brown <aaron.f.brown@intel.com>
>Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Conflict was because we don't have c8744f44aeae ("e1000e: Add Support
for CannonLake") on 4.9 and 4.4. I've worked around that and queued this
patch for both of those branches.
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-06-23 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 11:58 FAILED: patch "[PATCH] e1000e: Do not wake up the system via WOL if device wakeup is" failed to apply to 4.9-stable tree gregkh
2020-06-23 13:53 ` Sasha Levin [this message]
2020-06-24 13:22 ` 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=20200623135342.GZ1931@sasha-vm \
--to=sashal@kernel.org \
--cc=Stable@vger.kernel.org \
--cc=aaron.f.brown@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=rafael.j.wysocki@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox