From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 5.15 000/411] 5.15.186-rc1 review
Date: Mon, 21 Jul 2025 15:48:22 +0200 [thread overview]
Message-ID: <2025072105-tactics-flail-4035@gregkh> (raw)
In-Reply-To: <CAFBinCANe9oajzfZ_OGHoA-TtGC-CQdOm_O5TG8ke8m_NNE5NQ@mail.gmail.com>
On Mon, Jul 14, 2025 at 09:56:11PM +0200, Martin Blumenstingl wrote:
> Hi Greg,
>
> On Sat, Jul 12, 2025 at 2:37 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Jul 08, 2025 at 06:05:14PM +0200, Martin Blumenstingl wrote:
> > > Hi Guenter,
> > >
> > > On Mon, Jul 7, 2025 at 8:05 PM Guenter Roeck <linux@roeck-us.net> wrote:
> > > >
> > > > On Mon, Jun 23, 2025 at 03:02:24PM +0200, Greg Kroah-Hartman wrote:
> > > > > This is the start of the stable review cycle for the 5.15.186 release.
> > > > > There are 411 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 Wed, 25 Jun 2025 13:05:51 +0000.
> > > > > Anything received after that time might be too late.
> > > > >
> > > > ...
> > > > > Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> > > > > drm/meson: use unsigned long long / Hz for frequency types
> > > > >
> > > >
> > > > This patch triggers:
> > > >
> > > > Building arm:allmodconfig ... failed
> > > > --------------
> > > > Error log:
> > > > drivers/gpu/drm/meson/meson_vclk.c:399:17: error: this decimal constant is unsigned only in ISO C90 [-Werror]
> > > > 399 | .pll_freq = 2970000000,
> > > >
> > > > and other similar problems. This is with gcc 13.4.0.
> > > Sorry to hear that this is causing issues.
> > > Are you only seeing this with the backport on top of 5.15 or also on
> > > top of mainline or -next?
> > >
> > > If it's only for 5.15 then personally I'd be happy with just skipping
> > > this patch (and the ones that depend on it).
> >
> > It's already merged, and I see these errors in the Android build reports
> > now. I think they've just disabled the driver entirely to get around it :(
> Can you confirm that only 5.15 is affected - or do you also see
> problems with other stable versions?
>
> > > 5.15 is scheduled to be sunset in 16 months and I am not aware of many
> > > people running Amlogic SoCs with mainline 5.15.
> >
> > Great, can we send a "CONFIG_BROKEN" patch for this then?
> In my own words: you're asking for a patch for the next 5.15 release
> which adds "depends on BROKEN" to the meson drm driver. Is this
> correct?
Yes, given that it seems no one uses it there :)
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-21 13:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 13:02 [PATCH 5.15 000/411] 5.15.186-rc1 review Greg Kroah-Hartman
2025-06-23 20:42 ` Naresh Kamboju
2025-06-24 10:18 ` Greg Kroah-Hartman
2025-06-25 1:45 ` Naresh Kamboju
2025-06-25 8:39 ` Greg Kroah-Hartman
2025-11-06 19:32 ` Kees Cook
2025-11-21 9:36 ` Greg Kroah-Hartman
2025-11-21 18:00 ` Kees Cook
2025-11-27 13:46 ` Greg Kroah-Hartman
2025-06-23 20:49 ` Florian Fainelli
2025-06-24 8:39 ` Ron Economos
2025-06-25 7:23 ` Jon Hunter
2025-06-25 7:32 ` Vijayendra Suman
2025-07-07 18:05 ` Guenter Roeck
2025-07-08 16:05 ` Martin Blumenstingl
2025-07-12 12:37 ` Greg Kroah-Hartman
2025-07-14 19:56 ` Martin Blumenstingl
2025-07-21 13:48 ` Greg Kroah-Hartman [this message]
2025-07-21 14:12 ` Guenter Roeck
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=2025072105-tactics-flail-4035@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--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