On Tue, Aug 16, 2022 at 05:41:23PM +0100, Sudip Mukherjee wrote:
> On Tue, Aug 16, 2022 at 3:43 PM Greg Kroah-Hartman
> <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> >
> > On Tue, Aug 16, 2022 at 03:34:56PM +0100, Sudip Mukherjee wrote:
> > > Hi Greg,
> > >
> > > On Tue, Aug 16, 2022 at 1:59 PM Greg Kroah-Hartman
> > > <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> > > >
> > > > This is the start of the stable review cycle for the 5.18.18 release.
> > > > There are 1094 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 Thu, 18 Aug 2022 12:43:14 +0000.
> > > > Anything received after that time might be too late.
> > >
> > > The hung task problem I reported for v5.18.18-rc1 is not seen with rc2.
> >
> > Nice!
> >
> > > The drm warning is still there and a bisect pointed it to:
> > > 4b8701565b59 ("drm/vc4: hdmi: Move HDMI reset to
> > > pm_resume")4b8701565b59 ("drm/vc4: hdmi: Move HDMI reset to
> > > pm_resume")
> >
> > What drm warning?
>
> Reported for mainline now, at
> https://lore.kernel.org/lkml/YvvHK2zb1lbm2baU@debian/
Thanks, I'll wait for that to land in Linus's tree.
> > > I have not noticed earlier, the warning is there with mainline also. I
> > > will verify tonight and send another mail for mainline.
> >
> > Ah, ok, being bug compatible is good :)
> >
> > > Also, mips and csky allmodconfig build fails with gcc-12 due to
> > > 85d03e83bbfc ("Bluetooth: L2CAP: Fix l2cap_global_chan_by_psm
> > > regression").
> > > Mainline also has the same build failure reported at
> > > https://lore.kernel.org/lkml/YvY4xdZEWAPosFdJ@debian/
> >
> > Looks like they have a fix somewhere for that, any hints on where to
> > find it?
>
> There is a fix in the bluetooth tree master branch but it has not
> reached mainline yet. I will check which commit has fixed the failure
> and ping the bluetooth maintainers.
Same here, will just wait for that to land.
greg k-h
