Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> writes: > On Thu, Feb 01, 2024 at 06:43:46AM -0600, Justin Forbes wrote: >> Well, it appears that 6.6.15 shipped anyway, with this patch included, >> but not with 86a0adc029d3. If anyone else builds docs, this thread >> should at least show them the fix. Perhaps we can get the missing >> patch into 6.6.16? > > Sure, but again, that should be independent of this change, right? Yes, it's an independent change but seems worth backporting if people are running into the issue. Thanks, jon
