From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: stable@vger.kernel.org, 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, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com
Subject: Re: [PATCH 5.4 000/321] 5.4.287-rc1 review
Date: Fri, 13 Dec 2024 15:19:36 +0100 [thread overview]
Message-ID: <2024121312-retrieval-stencil-d02d@gregkh> (raw)
In-Reply-To: <975004ea-7eb0-4412-a9af-d10486df4bb7@sirena.org.uk>
On Fri, Dec 13, 2024 at 01:23:23PM +0000, Mark Brown wrote:
> On Thu, Dec 12, 2024 at 03:58:38PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.4.287 release.
> > There are 321 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.
>
> arm64 defconfig is failing to build with GCC 13 for me:
>
> /build/stage/linux/arch/arm64/include/asm/memory.h: In function ‘__tag_set’:
> /build/stage/linux/arch/arm64/include/asm/memory.h:238:22: warning: cast from po
> inter to integer of different size [-Wpointer-to-int-cast]
> 238 | u64 __addr = (u64)addr & ~__tag_shifted(0xff);
> | ^
> /tmp/ccGiqYDV.s: Assembler messages:
> /tmp/ccGiqYDV.s:129: Error: invalid barrier type -- `dmb ishld'
> /tmp/ccGiqYDV.s:234: Error: invalid barrier type -- `dmb ishld'
> /tmp/ccGiqYDV.s:510: Error: invalid barrier type -- `dmb ishld'
> /tmp/ccGiqYDV.s:537: Error: invalid barrier type -- `dmb ishld'
> /tmp/ccGiqYDV.s:1132: Error: invalid barrier type -- `dmb ishld'
> /tmp/ccGiqYDV.s:1216: Error: invalid barrier type -- `dmb ishld'
> make[2]: *** [/build/stage/linux/arch/arm64/kernel/vdso32/Makefile:166: arch/arm64/kernel/vdso32/vgettimeofday.o] Error 1
>
> I'm also seeing the 32 bit arm build errors Naresh reported.
Odd, it seems to work on clang here. Any chance you can bisect this
down to find the offending change?
thanks,
greg k-h
next prev parent reply other threads:[~2024-12-13 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 14:58 [PATCH 5.4 000/321] 5.4.287-rc1 review Greg Kroah-Hartman
2024-12-12 15:00 ` [PATCH 5.4 115/321] m68k: coldfire/device.c: only build FEC when HW macros are defined Greg Kroah-Hartman
2024-12-12 19:33 ` [PATCH 5.4 000/321] 5.4.287-rc1 review Pavel Machek
2024-12-12 19:53 ` Florian Fainelli
2024-12-12 20:24 ` Naresh Kamboju
2024-12-13 12:19 ` Greg Kroah-Hartman
2024-12-13 10:02 ` Jon Hunter
2024-12-13 13:23 ` Mark Brown
2024-12-13 14:19 ` Greg Kroah-Hartman [this message]
2024-12-14 12:47 ` 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=2024121312-retrieval-stencil-d02d@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=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