From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.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, allen.lkml@gmail.com, broonie@kernel.org,
Anders Roxell <anders.roxell@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH 5.15 00/87] 5.15.164-rc1 review
Date: Fri, 26 Jul 2024 08:33:00 +0200 [thread overview]
Message-ID: <2024072645-delighted-barbecue-154f@gregkh> (raw)
In-Reply-To: <CA+G9fYvCyg1hXaci_j-RB4YgATb458ZqRjJSye4qub9zYrmL_A@mail.gmail.com>
On Thu, Jul 25, 2024 at 10:18:49PM +0530, Naresh Kamboju wrote:
> On Thu, 25 Jul 2024 at 20:22, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 5.15.164 release.
> > There are 87 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 Sat, 27 Jul 2024 14:27:16 +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.15.164-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.15.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> The following build errors noticed while building arm configs with toolchains
> gcc-12 and clang-18 on stable-rc linux-5.15.y
>
> First seen on today builds 25-July-2024.
>
> GOOD: b84034c8f228 ("Linux 5.15.163-rc2")
> BAD: 1d0703aa8114 ("Linux 5.15.164-rc1")
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Build log:
> -------
> from drivers/net/wireless/ralink/rt2x00/rt2800lib.c:25:
> drivers/net/wireless/ralink/rt2x00/rt2800lib.c: In function
> 'rt2800_txpower_to_dev':
> include/linux/build_bug.h:78:41: error: static assertion failed:
> "clamp() low limit (char)(-7) greater than high limit (char)(15)"
> 78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
> | ^~~~~~~~~~~~~~
> include/linux/build_bug.h:77:34: note: in expansion of macro '__static_assert'
> 77 | #define static_assert(expr, ...) __static_assert(expr,
> ##__VA_ARGS__, #expr)
> | ^~~~~~~~~~~~~~~
> include/linux/minmax.h:66:17: note: in expansion of macro 'static_assert'
> 66 |
> static_assert(__builtin_choose_expr(__is_constexpr((lo) > (hi)),
> \
> | ^~~~~~~~~~~~~
> include/linux/minmax.h:76:17: note: in expansion of macro '__clamp_once'
> 76 | __clamp_once(val, lo, hi, __UNIQUE_ID(__val),
> \
> | ^~~~~~~~~~~~
> include/linux/minmax.h:180:36: note: in expansion of macro '__careful_clamp'
> 180 | #define clamp_t(type, val, lo, hi)
> __careful_clamp((type)(val), (type)(lo), (type)(hi))
> | ^~~~~~~~~~~~~~~
> drivers/net/wireless/ralink/rt2x00/rt2800lib.c:3993:24: note: in
> expansion of macro 'clamp_t'
> 3993 | return clamp_t(char, txpower, MIN_A_TXPOWER,
> MAX_A_TXPOWER);
> | ^~~~~~~
>
Thanks, I've added a commit that should resolve this now. I'll push out
a -rc2 in a bit.
greg k-h
next prev parent reply other threads:[~2024-07-26 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 14:36 Greg Kroah-Hartman
2024-07-25 16:48 ` Naresh Kamboju
2024-07-26 6:33 ` Greg Kroah-Hartman [this message]
2024-07-26 8:15 ` Pavel Machek
2024-07-25 23:19 ` SeongJae Park
2024-07-26 5:23 ` Harshit Mogalapalli
2024-07-26 16:38 ` Shuah Khan
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=2024072645-delighted-barbecue-154f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@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
all inboxes | Powered by JetHome®