Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20220816124604.978842485@linuxfoundation.org> <CADVatmPOCPfHQHEuwVmOb5oeN2HfWWMztVok3qvoq7Ndndb14A@mail.gmail.com>
 <YvutIhMRZW/nKOPi@kroah.com> <CADVatmM4ZH0PvPiFrdwqXg5y-w4Z3=7YqLz9SW54ygScoODPmQ@mail.gmail.com>
In-Reply-To: <CADVatmM4ZH0PvPiFrdwqXg5y-w4Z3=7YqLz9SW54ygScoODPmQ@mail.gmail.com>
From:   Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Date:   Tue, 16 Aug 2022 17:57:58 +0100
Message-ID: <CADVatmP2L05SoUNKEbfF0-msB_Bz+dga+PDAK6Ncx5OTJL0oaQ@mail.gmail.com>
Subject: Re: [PATCH 5.18 0000/1094] 5.18.18-rc2 review
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Tue, Aug 16, 2022 at 5:41 PM Sudip Mukherjee
<sudipm.mukherjee@gmail.com> 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.
> > > >

<snip>

> > > 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.

No, sorry, bluetooth master branch does not have the offending commit.

So, there are two prospective fixes.
https://lore.kernel.org/lkml/20220811124637.4cdb84f1@kernel.org/
and
https://lore.kernel.org/linux-bluetooth/20220812055249.8037-1-palmer@rivosinc.com/T/#m31035e486a2fc7d4f927073295a945743b77a55a


-- 
Regards
Sudip