On Thu, Feb 29, 2024 at 12:13 AM Brennan Lamoreaux <brennan.lamoreaux@xxxxxxxxxxxx> wrote: > > > If you provide a working backport of that commit, we will be glad to > > apply it. As-is, it does not apply at all, which is why it was never > > added to the 6.1.y tree. > > Oh, apologies for requesting if they don't apply. I'd be happy to submit > working backports for these patches, but I am not seeing any issues applying/building > the patches on my machine... Both patches in sequence applied directly and my > local build was successful. > > This is the workflow I tested: > > git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.1.y > git checkout FETCH_HEAD > git cherry-pick -x 8d037973d48c026224ab285e6a06985ccac6f7bf > git cherry-pick -x 0e15863015d97c1ee2cc29d599abcc7fa2dc3e95 > make allyesconfig > make > > Please let me know if I've made a mistake with the above commands, or if these patches aren't applicable > for some other reason. > I guess the reason is: 8d037973d48c026224ab285e6a06985ccac6f7bf doesn't have "Fixes:" and is not sent to stable@xxxxxxxxxxxxxxx. And 0e15863015d97c1ee2cc29d599abcc7fa2dc3e95 is to Fix 8d037973d48c026224ab285e6a06985ccac6f7bf, so no need of 0e158 if 8d03 not backported to that particular branch. - Ajay
