On 9/26/19 12:43 AM, Sasha Levin wrote:
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag, fixing commit: 1da177e4c3f4 Linux-2.6.12-rc2.
The bot has tested the following trees: v5.3.1, v5.2.17, v4.19.75, v4.14.146, v4.9.194, v4.4.194.
v5.3.1: Build OK! v5.2.17: Build OK! v4.19.75: Build OK! v4.14.146: Failed to apply! Possible dependencies: 75492a51568b ("s390/scsi: Convert timers to use timer_setup()")
v4.9.194: Failed to apply! Possible dependencies: 75492a51568b ("s390/scsi: Convert timers to use timer_setup()") bc46427e807e ("scsi: zfcp: use setup_timer instead of init_timer")
v4.4.194: Failed to apply! Possible dependencies: 75492a51568b ("s390/scsi: Convert timers to use timer_setup()") bc46427e807e ("scsi: zfcp: use setup_timer instead of init_timer")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
It's sufficient to have the fix in those more recent stable trees where it applies (and builds). My fixes tag formally indicates since when it was at least broken but I don't expect all stable or longterm kernels to get the fix. If I happen to find out we need the fix in a kernel where it does not apply, I'll send a backport to stable when the time is right.
Showing the possible dependencies is awesome!