From: "Daniel Díaz" <daniel.diaz@linaro.org>
To: Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, florian.fainelli@broadcom.com,
pavel@denx.de, abelova@astralinux.ru
Subject: Re: [PATCH 4.19 000/147] 4.19.311-rc2 review
Date: Mon, 25 Mar 2024 17:56:22 -0600 [thread overview]
Message-ID: <83814bca-1e33-4914-b00d-4b84ff1a1a23@linaro.org> (raw)
In-Reply-To: <20240325115854.1764898-1-sashal@kernel.org>
Hello!
On 25/03/24 5:58 a. m., Sasha Levin wrote:
> This is the start of the stable review cycle for the 4.19.311 release.
> There are 147 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 Mar 27 11:58:33 AM UTC 2024.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-4.19.y&id2=v4.19.310
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y
> and the diffstat can be found below.
>
> Thanks,
> Sasha
As with 5.4, we see a new warning on Arm (32- and 64-bits):
-----8<-----
/builds/linux/drivers/cpufreq/brcmstb-avs-cpufreq.c: In function 'brcm_avs_cpufreq_get':
/builds/linux/drivers/cpufreq/brcmstb-avs-cpufreq.c:462:2: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
struct private_data *priv = policy->driver_data;
^~~~~~
----->8-----
Bisection pointed to:
commit 2b373882d724311d7a5dadf225ed296f20abc8f9
Author: Anastasia Belova <abelova@astralinux.ru>
Date: Wed Jan 17 10:12:20 2024 +0300
cpufreq: brcmstb-avs-cpufreq: add check for cpufreq_cpu_get's return value
[ Upstream commit f661017e6d326ee187db24194cabb013d81bc2a6 ]
Reproducer:
tuxmake --runtime podman --target-arch arm64 --toolchain gcc-8 --kconfig defconfig
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Greetings!
Daniel Díaz
daniel.diaz@linaro.org
next prev parent reply other threads:[~2024-03-25 23:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 11:58 Sasha Levin
2024-03-25 19:01 ` Pavel Machek
2024-03-25 23:56 ` Daniel Díaz [this message]
2024-03-26 9:09 ` Naresh Kamboju
2024-03-26 12:37 ` Naresh Kamboju
2024-03-28 14:07 ` Naresh Kamboju
2024-03-26 17:24 ` Shuah Khan
2024-03-27 9:04 ` Harshit Mogalapalli
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=83814bca-1e33-4914-b00d-4b84ff1a1a23@linaro.org \
--to=daniel.diaz@linaro.org \
--cc=abelova@astralinux.ru \
--cc=akpm@linux-foundation.org \
--cc=florian.fainelli@broadcom.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=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--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
all inboxes | Powered by JetHome®