On Tue, Jul 01, 2025 at 01:42:05PM +0300, Joonas Lahtinen wrote:
Hi Greg,
Please do note that there is a revert for this patch that was part of the same pull request. That needs to be picked in too in case you are picking the original patch.
I already got the automated mails from Sasha that both the original commit and revert were already picked into 6.1, 6.6 and 6.12 trees. Are now in a perpetual machinery induced loop where the original commit and revert will be picked in alternating fashion to the stable trees? [1]
Yes.
Regards, Joonas
[1] Originally, I was under the assumption stable machinery would automatically skip over patches that have later been reverted, but that doesn't seem to be the case?
Nope, if that were to happen then we would be adding it back over time as we would go "hey, we missed this one!" all the time. Adding the commit and revert is best.
thanks
greg k-h