From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Stable <stable@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>, Shuah Khan <shuah@kernel.org>,
patches@kernelci.org, lkft-triage@lists.linaro.org,
Pavel Machek <pavel@denx.de>,
Jonathan Hunter <jonathanh@nvidia.com>,
Florian Fainelli <f.fainelli@gmail.com>,
slade@sladewatkins.com
Subject: Re: [PATCH 5.18 0000/1094] 5.18.18-rc2 review
Date: Wed, 17 Aug 2022 13:39:08 +0200 [thread overview]
Message-ID: <YvzTXOKsbSfDpLjZ@kroah.com> (raw)
In-Reply-To: <CADVatmM4ZH0PvPiFrdwqXg5y-w4Z3=7YqLz9SW54ygScoODPmQ@mail.gmail.com>
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@linuxfoundation.org> 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@linuxfoundation.org> 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
next prev parent reply other threads:[~2022-08-17 11:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 12:59 [PATCH 5.18 0000/1094] 5.18.18-rc2 review Greg Kroah-Hartman
2022-08-16 14:34 ` Sudip Mukherjee
2022-08-16 14:43 ` Greg Kroah-Hartman
2022-08-16 16:25 ` Naresh Kamboju
2022-08-16 16:41 ` Sudip Mukherjee
2022-08-16 16:57 ` Sudip Mukherjee
2022-08-17 11:39 ` Greg Kroah-Hartman [this message]
2022-08-16 19:15 ` Naresh Kamboju
2022-08-17 7:25 ` Maxime Ripard
2022-08-17 0:59 ` Ron Economos
2022-08-17 4:24 ` Guenter Roeck
2022-08-17 13:34 ` Greg Kroah-Hartman
2022-08-17 15:24 ` Guenter Roeck
2022-08-17 12:57 ` Justin Forbes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YvzTXOKsbSfDpLjZ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=slade@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox