[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200618131802.16B042073E@mail.kernel.org>
Date: Thu, 18 Jun 2020 13:18:01 +0000
From: Sasha Levin <sashal@...nel.org>
To: davem@...emloft.net
Cc: stable@...r.kernel.org
Subject: Re: [net 1/3] e1000e: Do not wake up the system via WOL if device wakeup is disabled
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.7.2, v5.4.46, v4.19.128, v4.14.184, v4.9.227, v4.4.227.
v5.7.2: Build OK!
v5.4.46: Build OK!
v4.19.128: Build OK!
v4.14.184: Build OK!
v4.9.227: Failed to apply! Possible dependencies:
c8744f44aeaee ("e1000e: Add Support for CannonLake")
v4.4.227: Failed to apply! Possible dependencies:
16ecba59bc333 ("e1000e: Do not read ICR in Other interrupt")
18dd239207038 ("e1000e: use BIT() macro for bit defines")
74f31299a41e7 ("e1000e: Increase PHY PLL clock gate timing")
c8744f44aeaee ("e1000e: Add Support for CannonLake")
f3ed935de059b ("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
Powered by blists - more mailing lists