From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: 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,
achill@achill.org
Subject: Re: [PATCH 6.12 000/438] 6.12.43-rc2 review
Date: Fri, 22 Aug 2025 10:16:25 +0200 [thread overview]
Message-ID: <2025082231-upstairs-blinks-1f4e@gregkh> (raw)
In-Reply-To: <63e25fdb-095a-40eb-b341-75781e71ea95@roeck-us.net>
On Thu, Aug 21, 2025 at 08:12:27AM -0700, Guenter Roeck wrote:
> On Tue, Aug 19, 2025 at 02:31:21PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.12.43 release.
> > There are 438 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 Thu, 21 Aug 2025 12:27:16 +0000.
> > Anything received after that time might be too late.
> >
>
> Build reference: v6.12.43
> Compiler version: arm-linux-gnueabi-gcc (GCC) 14.3.0
> Assembler version: GNU assembler (GNU Binutils) 2.44
>
> Configuration file workarounds:
> "s/CONFIG_FRAME_WARN=.*/CONFIG_FRAME_WARN=0/"
>
> Building arm:allmodconfig ... failed
> --------------
> Error log:
> drivers/net/can/ti_hecc.c: In function 'ti_hecc_start':
> drivers/net/can/ti_hecc.c:386:21: error: implicit declaration of function 'BIT_U32'; did you mean 'BIT_ULL'? [-Wimplicit-function-declaration]
> 386 | mbx_mask = ~BIT_U32(HECC_RX_LAST_MBOX);
> | ^~~~~~~
> | BIT_ULL
>
> There is no BIT_U32 in v6.12.y. The same build error is seen in v6.15.11,
> which is also missing the definition of BIT_U32. Odd that no one seems
> to have noticed this. Am I missing something ?
I'm now seeing this as well. I'm guessing no one else does arm32 full
builds anymore? I guess no one cares about that platform anymore :(
I'll go revert the offending commit, thanks for letting me know.
greg k-h
prev parent reply other threads:[~2025-08-22 8:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 12:31 [PATCH 6.12 000/438] 6.12.43-rc2 review Greg Kroah-Hartman
2025-08-19 13:34 ` Peter Schneider
2025-08-19 16:27 ` Harshit Mogalapalli
2025-08-19 20:14 ` Florian Fainelli
2025-08-20 7:11 ` Pavel Machek
2025-08-20 7:26 ` Hardik Garg
2025-08-20 9:14 ` Brett A C Sheffield
2025-08-20 10:59 ` [PATCH 6.12 000/438] " Mark Brown
2025-08-20 12:45 ` Naresh Kamboju
2025-08-20 13:26 ` Brett Mastbergen
2025-08-20 14:07 ` Jon Hunter
2025-08-20 14:49 ` Mark Brown
2025-08-21 15:12 ` Guenter Roeck
2025-08-22 8:16 ` Greg Kroah-Hartman [this message]
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=2025082231-upstairs-blinks-1f4e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=achill@achill.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