Re: [PATCH 6.18 000/675] 6.18.42-rc1 review
Greg KH <[email protected]> Fri, 31 Jul 2026 08:57:05 +0200
| Newsgroups | dev.linux.lists.patches,org.freedesktop.lists.dri-devel,org.kernel.vger.linux-kernel,org.kernel.vger.stable |
|---|---|
| Message-ID | <2026073106-ajar-mantis-9f4e@gregkh> |
On Thu, Jul 30, 2026 at 08:17:17PM +0200, Miguel Ojeda wrote: > On Thu, 30 Jul 2026 16:05:30 +0200 Greg Kroah-Hartman <[email protected]> wrote: > > > > This is the start of the stable review cycle for the 6.18.42 release. > > There are 675 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Sat, 01 Aug 2026 14:13:45 +0000. > > Anything received after that time might be too late. > > Boot-tested under QEMU for Rust x86_64, arm64 and riscv64; built-tested > for loongarch64 and arm32: > > Tested-by: Miguel Ojeda <[email protected]> > > I detected in the middle of the build lines like: > > find: 'lib': No such file or directory > > It looks like we need: > > ee8bfb15d02d ("drm: drop lib from header search path.") > > to go together with the one that was backported: > > 5e7b3c10420e ("gpu: Move DRM buddy allocator one level up (part two)") > > Having said that, there is something going on a bit confusing: commits > "part one" (4a9671a03f2b) and "part two" (ba110db8e1bc) in mainline seem > to have been merged into just the "part two" above in this -rc. Is that > intentional? I am asking because the original removal of the `lib` > folder happened in "part one" in mainline, so I was expecting to have to > point to that one above, but it doesn't exist on its own. > > Cc: Joel Fernandes <[email protected]> > Cc: David Airlie <[email protected]> > Cc: Simona Vetter <[email protected]> > Cc: [email protected] Odd, looks like Sasha did it in one backport instead of two, perhaps because we wanted a real patch and not a "move" patch? Anyway, I'll go take the fixup change now too, thanks! greg k-h