On 30.10.23 13:42, Greg KH wrote:
20 patches is trivial for us to handle, please do it that way as it ensures we keep the proper history, AND we know what to backport when in the future.
Ok, will do.
When you try to crunch patches together, or do non-upstream changes, 90%+ of the time they end up being wrong or impossible to maintain over time.
Ok, then I will maintain the entire history of fixes of fixes without crunching them together.
But why just 5.15? What about 6.1.y and 6.5.y?I have posted 5.10 and 5.15 for now. 6.1 would be only this patch 96d1c81e6a04 ("can: isotp: add module parameter for maximum pdu size") I can also provide.Why add new features to older kernels? That's not going to be ok, sorry.
I will drop the module parameter stuff then, as it has no impact on the communication state machine that is in the focus to be consistently fixed and updated to the 6.6 code base. Then everything in 5.15 and 5.10 will be on the same level as 6.1. This will ease further fixes and maintenance.
Best regards, Oliver
