+++ Sasha Levin [17/03/20 22:30 +0000]:
Hi
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.5.9, v5.4.25, v4.19.109, v4.14.173, v4.9.216, v4.4.216.
v5.5.9: Build OK!
v5.4.25: Build OK!
v4.19.109: Build OK!
v4.14.173: Build OK!
v4.9.216: Failed to apply! Possible dependencies:
41124db869b7 ("fs: warn in case userspace lied about modprobe return")
v4.4.216: Failed to apply! Possible dependencies:
41124db869b7 ("fs: warn in case userspace lied about modprobe return")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
Since commit 41124db869b7 was introduced v4.13, I guess we should
change the stable tag to:
Cc: stable@xxxxxxxxxxxxxxx # v4.13+
