On Fri, Sep 04, 2020 at 04:17:48PM +0200, SeongJae Park wrote:
<snip>
Stopping right here, if you have fixes that will not cleanly apply, and you think they should be applied, please fix them and send the proper backport. I don't have the cycles to do these on my own.
Same for anything else here that you think should be applied but does not cleanly build/apply.
Totally agreed. Actually, I posted a similar report[1] before and received similar response. I promised to back-port some of those by myself. That's still in my TODO list, but I was unable to get a time to revisit it quite long time. From this, I realized that it wouldn't be easy to review, test, and backport all of the such suspicious things by myself. Scaling up to multiple stable series (the tool says there are 152 fixes and 147 mentions for 4.9.y) seems impossible.
For the reason, I updated the tool to make the report to be sent to not only the stable maintainers but also the authors of the suspicious commits, because the review / test / backport of their own commits would be much easier that others. As a result, we were able to find one suspended commit: https://lore.kernel.org/stable/CAKfTPtAkOes+HmVabRazhCBBUo0M+QW38q3Zzj_O3O+G...
That work had already been done before your email was sent.
I too can write a tool that sends out "this patch might be for stable, will you do the work for it!" emails, but that's a bit rude to ask others to do your work for you, don't you agree? By asking me and others to dig through this list, when you said you don't have the time to do so, feels very odd to me.
And if you have only 152 "fixes" for 4.9.y, that's great, should be easy to work through. I do know that most of the "easy" backports are already done, so what is left are the ones that take real work, or do not make any sense, as your list shows.
So I don't think this report actually helped anyone here, do you?
Again, if you can do the backporting, that will help out greatly.
thanks,
greg k-h