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: 9.2381)
The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126,
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 Thu, 05 Apr 2018, Sasha Levin wrote:
This commit has been processed by the -stable helper bot and determined to be a high probability candidate for -stable trees. (score: 9.2381)
The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126,
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.
As far as I am concerned, yes, after a suitable period in mainline.
What would be a suitable period in mainline I'd rather be set by the subsystem maintainer. But this is a very low risk patch, if it worked in mainline, it will work anywhere it compiles.
linux-stable-mirror@lists.linaro.org