From: Jon Hunter <jonathanh@nvidia.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: patches@lists.linux.dev, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@denx.de,
f.fainelli@gmail.com, sudipm.mukherjee@gmail.com,
srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org,
linux-tegra@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 5.4 000/222] 5.4.295-rc1 review
Date: Wed, 25 Jun 2025 08:34:47 +0100 [thread overview]
Message-ID: <c84768f2-17d7-4edd-8f6e-d0f2a74ef559@nvidia.com> (raw)
In-Reply-To: <cf271495-270e-4a0a-a93e-fe8c44e4eabd@rnnvmail204.nvidia.com>
Hi Greg,
On 25/06/2025 08:16, Jon Hunter wrote:
> On Mon, 23 Jun 2025 15:05:35 +0200, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 5.4.295 release.
>> There are 222 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:50 +0000.
>> Anything received after that time might be too late.
>>
>> The whole patch series can be found in one patch at:
>> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.295-rc1.gz
>> or in the git tree and branch at:
>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.4.y
>> and the diffstat can be found below.
>>
>> thanks,
>>
>> greg k-h
>
> Failures detected for Tegra ...
>
> Test results for stable-v5.4:
> 10 builds: 7 pass, 3 fail
> 18 boots: 18 pass, 0 fail
> 39 tests: 39 pass, 0 fail
>
> Linux version: 5.4.295-rc1-gca8c5417d1e6
> Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
> tegra194-p2972-0000, tegra20-ventana,
> tegra210-p2371-2180, tegra210-p3450-0000,
> tegra30-cardhu-a04
>
> Builds failed: arm+multi_v7
I am seeing the following build error for ARM with the
multi_v7_defconfig on our builders ...
CC drivers/firmware/qcom_scm-32.o
/tmp/cc9gP1cd.s: Assembler messages:
/tmp/cc9gP1cd.s:45: Error: selected processor does not support `smc #0' in ARM mode
/tmp/cc9gP1cd.s:94: Error: selected processor does not support `smc #0' in ARM mode
/tmp/cc9gP1cd.s:160: Error: selected processor does not support `smc #0' in ARM mode
/tmp/cc9gP1cd.s:295: Error: selected processor does not support `smc #0' in ARM mode
make[3]: *** [/home/jonathanh/nvidia/mlt-linux_next/kernel/scripts/Makefile.build:262: drivers/firmware/qcom_scm-32.o] Error 1
Bisect is pointing to ...
# first bad commit: [0c23125c509b41be51f0d5acb843b079a098a40c] kbuild: Update assembler calls to use proper flags and language target
Reverting this fixes it but I also needed to revert the following due to dependencies ...
Nathan Chancellor <nathan@kernel.org>
kbuild: Add KBUILD_CPPFLAGS to as-option invocation
Nathan Chancellor <nathan@kernel.org>
kbuild: Add CLANG_FLAGS to as-instr
Jon
--
nvpublic
next prev parent reply other threads:[~2025-06-25 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250623130611.896514667@linuxfoundation.org>
2025-06-25 7:16 ` [PATCH 5.4 000/222] 5.4.295-rc1 review Jon Hunter
2025-06-25 7:34 ` Jon Hunter [this message]
2025-06-25 8:52 ` Greg Kroah-Hartman
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=c84768f2-17d7-4edd-8f6e-d0f2a74ef559@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--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