Greg KH wrote: > On Fri, May 03, 2024 at 09:48:05AM -0700, John Fastabend wrote: > > [ Upstream commit ebf2e8860eea66e2c4764316b80c6a5ee5f336ee] > > [ Upstream commit f8dd95b29d7ef08c19ec9720564acf72243ddcf6] > > Why are you mushing 2 patches together? Why can't we just take the two > as-is instead? That makes tracking everything much simpler and > possible. OK the thought was to get the minimal diff needed. But that is problematic. We can take the first one as-is and then the second one will have a couple chunks that don't apply but we don't need those chunks because the infiniband part it touches doesn't have the same issue in 6.1. > > > In the first patch, [...] > > For the backport we isolated the fix to the two lines in the above > > patches that fixed the code. With this patch we deployed the workloads > > again and error rates and stalls went away and 6.1 stable kernels > > perform similar to 6.5 stable kernels. Similarly the compliance tests > > also passed. > > Can we just take the two original patches instead? Yes minus the couple chunks that don't apply on the second one. I'll do some testing and resend thanks. > > thanks, > > greg k-h
