Hi,
[This is an automated email]
This commit has been processed by the -stable helper bot and determined to be a high probability candidate for -stable trees. (score: 16.2224)
The bot has tested the following trees: v4.16, v4.15.15, v4.14.32, v4.9.92, v4.4.126.
v4.16: Build OK! v4.15.15: Build OK! v4.14.32: Build OK! v4.9.92: Build OK! v4.4.126: Build OK!
Please let us know if you'd like to have this patch included in a stable tree.
-- Thanks, Sasha
On Mon, Apr 9, 2018 at 5:37 AM, Sasha Levin Alexander.Levin@microsoft.com wrote:
Hi,
[This is an automated email]
This commit has been processed by the -stable helper bot and determined to be a high probability candidate for -stable trees. (score: 16.2224)
The bot has tested the following trees: v4.16, v4.15.15, v4.14.32, v4.9.92, v4.4.126.
v4.16: Build OK! v4.15.15: Build OK! v4.14.32: Build OK! v4.9.92: Build OK! v4.4.126: Build OK!
Please let us know if you'd like to have this patch included in a stable tree.
Sounds, like something reasonable to do, though there should not be any device in the wild triggering these conditions right now.
I'll add the proper tags in v2.
Cheers, Benjamin
-- Thanks, Sasha
linux-stable-mirror@lists.linaro.org