On Mon, Jun 24, 2019 at 09:01:27AM +0200, Krzysztof Kozlowski wrote:
On Sat, 22 Jun 2019 at 20:13, Sasha Levin sashal@kernel.org wrote:
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag, fixing commit: 1c984942f0a4 regulator: s2mps11: Pass descriptor instead of GPIO number.
The bot has tested the following trees: v5.1.12, v4.19.53.
v5.1.12: Build OK! v4.19.53: Failed to apply! Possible dependencies: Unable to calculate
How should we proceed with this patch?
The commit mentioned in fixes tag (1c984942f0a4) came in v5.0-rc1/v5.0. Why do you try to port it to v4.19?
This is an interesting one! Usually when something like this happens, it means that the "fixed" commit was backported to stable, but as you pointed out, it was not.
My scripts have logic to try and detect these backports, and it appears that there's a commit with an identical subject line in the 4.19 tree, so at this point there are two commits with identical subject lines in Linus's tree:
1c984942f0a4 regulator: s2mps11: Pass descriptor instead of GPIO number 0369e02b75e6 regulator: s2mps11: Pass descriptor instead of GPIO number
Which can be confusing for humans too :)
-- Thanks, Sasha