From: Sasha Levin <sashal@kernel.org>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 1/2] e1000e: Do not wake up the system via WOL if device wakeup is disabled
Date: Tue, 26 May 2020 00:23:55 +0000 [thread overview]
Message-ID: <20200526002355.B2FAE20657@mail.kernel.org> (raw)
In-Reply-To: <9f7ede2e2e8152704258fc11ba3755ae93f50741.1590081982.git.yu.c.chen@intel.com>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: bc7f75fa9788 ("[E1000E]: New pci-express e1000 driver (currently for ICH9 devices only)").
The bot has tested the following trees: v5.6.14, v5.4.42, v4.19.124, v4.14.181, v4.9.224, v4.4.224.
v5.6.14: Build OK!
v5.4.42: Build OK!
v4.19.124: Build OK!
v4.14.181: Build OK!
v4.9.224: Failed to apply! Possible dependencies:
c8744f44aeae ("e1000e: Add Support for CannonLake")
v4.4.224: Failed to apply! Possible dependencies:
16ecba59bc33 ("e1000e: Do not read ICR in Other interrupt")
18dd23920703 ("e1000e: use BIT() macro for bit defines")
74f31299a41e ("e1000e: Increase PHY PLL clock gate timing")
c8744f44aeae ("e1000e: Add Support for CannonLake")
f3ed935de059 ("e1000e: initial support for i219-LM (3)")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Chen Yu <yu.c.chen@intel.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Cc: <Stable@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/2] e1000e: Do not wake up the system via WOL if device wakeup is disabled
Date: Tue, 26 May 2020 00:23:55 +0000 [thread overview]
Message-ID: <20200526002355.B2FAE20657@mail.kernel.org> (raw)
In-Reply-To: <9f7ede2e2e8152704258fc11ba3755ae93f50741.1590081982.git.yu.c.chen@intel.com>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: bc7f75fa9788 ("[E1000E]: New pci-express e1000 driver (currently for ICH9 devices only)").
The bot has tested the following trees: v5.6.14, v5.4.42, v4.19.124, v4.14.181, v4.9.224, v4.4.224.
v5.6.14: Build OK!
v5.4.42: Build OK!
v4.19.124: Build OK!
v4.14.181: Build OK!
v4.9.224: Failed to apply! Possible dependencies:
c8744f44aeae ("e1000e: Add Support for CannonLake")
v4.4.224: Failed to apply! Possible dependencies:
16ecba59bc33 ("e1000e: Do not read ICR in Other interrupt")
18dd23920703 ("e1000e: use BIT() macro for bit defines")
74f31299a41e ("e1000e: Increase PHY PLL clock gate timing")
c8744f44aeae ("e1000e: Add Support for CannonLake")
f3ed935de059 ("e1000e: initial support for i219-LM (3)")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-05-26 0:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 17:58 [Intel-wired-lan] [PATCH 0/2] Make WOL of e1000e consistent with sysfs device wakeup Chen Yu
2020-05-21 17:58 ` Chen Yu
2020-05-21 17:59 ` [Intel-wired-lan] [PATCH 1/2] e1000e: Do not wake up the system via WOL if device wakeup is disabled Chen Yu
2020-05-21 17:59 ` Chen Yu
2020-05-26 0:23 ` Sasha Levin [this message]
2020-05-26 0:23 ` Sasha Levin
2020-05-26 3:34 ` [Intel-wired-lan] " Chen Yu
2020-05-26 3:34 ` Chen Yu
2020-06-15 18:51 ` [Intel-wired-lan] " Brown, Aaron F
2020-06-15 18:51 ` Brown, Aaron F
2020-06-16 7:01 ` [Intel-wired-lan] " Chen Yu
2020-06-16 7:01 ` Chen Yu
2020-05-21 17:59 ` [Intel-wired-lan] [PATCH 2/2] e1000e: Make WOL info in ethtool consistent with device wake up ability Chen Yu
2020-05-21 17:59 ` Chen Yu
2020-05-21 19:23 ` [Intel-wired-lan] " Michal Kubecek
2020-05-21 19:23 ` Michal Kubecek
2020-05-23 9:09 ` [Intel-wired-lan] " Chen Yu
2020-05-23 9:09 ` Chen Yu
2020-05-24 21:06 ` [Intel-wired-lan] " Michal Kubecek
2020-05-24 21:06 ` Michal Kubecek
2020-05-25 16:12 ` [Intel-wired-lan] " Chen Yu
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=20200526002355.B2FAE20657@mail.kernel.org \
--to=sashal@kernel.org \
--cc=intel-wired-lan@osuosl.org \
/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.