The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Anders Roxell <anders.roxell@linaro.org>
Subject: Re: [PATCH 6.6 00/91] 6.6.52-rc1 review
Date: Wed, 18 Sep 2024 08:17:07 +0200	[thread overview]
Message-ID: <2024091853-thickness-plexiglas-5e83@gregkh> (raw)
In-Reply-To: <CA+G9fYv+OXhNPn87X4O9w8-HzGP04USge-et0b3Y4ncU9tussg@mail.gmail.com>

On Tue, Sep 17, 2024 at 04:00:10PM +0530, Naresh Kamboju wrote:
> On Mon, 16 Sept 2024 at 17:38, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 6.6.52 release.
> > There are 91 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, 18 Sep 2024 11:42:05 +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/v6.x/stable-review/patch-6.6.52-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-6.6.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> 
> 
> The s390 builds failed on the Linux stable-rc linux-6.6.y and linux-6.10.y due
> to following build warnings / errors with gcc-13 and clang-19 with defconfig.
> 
> * s390, build
>   - clang-19-allnoconfig
>   - clang-19-defconfig
>   - clang-19-tinyconfig
>   - clang-nightly-allnoconfig
>   - clang-nightly-defconfig
>   - clang-nightly-tinyconfig
>   - gcc-13-allmodconfig
>   - gcc-13-allnoconfig
>   - gcc-13-defconfig
>   - gcc-13-tinyconfig
>   - gcc-8-allnoconfig
>   - gcc-8-defconfig-fe40093d
>   - gcc-8-tinyconfig
> 
> 
> First seen on v6.6.51-92-gfd49ddc1e5f8
>   Good: v6.6.51
>   BAD:  v6.6.51-92-gfd49ddc1e5f8
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> build log:
> --------
> arch/s390/kernel/setup.c: In function 'reserve_lowcore':
> arch/s390/kernel/setup.c:748:31: error: implicit declaration of
> function 'get_lowcore'; did you mean 'setup_lowcore'?
> [-Werror=implicit-function-declaration]
>   748 |         void *lowcore_start = get_lowcore();
>       |                               ^~~~~~~~~~~
>       |                               setup_lowcore
> arch/s390/kernel/setup.c:748:31: warning: initialization of 'void *'
> from 'int' makes pointer from integer without a cast
> [-Wint-conversion]
> arch/s390/kernel/setup.c:752:21: error: '__identity_base' undeclared
> (first use in this function)
>   752 |         if ((void *)__identity_base < lowcore_end) {
>       |                     ^~~~~~~~~~~~~~~
> arch/s390/kernel/setup.c:752:21: note: each undeclared identifier is
> reported only once for each function it appears in
> In file included from include/linux/bits.h:21,
>                  from arch/s390/include/asm/ptrace.h:10,
>                  from arch/s390/include/asm/lowcore.h:13,
>                  from arch/s390/include/asm/current.h:13,
>                  from include/linux/sched.h:12,
>                  from arch/s390/kernel/setup.c:21:
> include/linux/minmax.h:31:9: error: first argument to
> '__builtin_choose_expr' not a constant
>    31 |
> __builtin_choose_expr(__is_constexpr(is_signed_type(typeof(x))),
>  \
>       |         ^~~~~~~~~~~~~~~~~~~~~

Offending commit now removed from 6.6.y and 6.10.y, thanks!

greg k-h

  reply	other threads:[~2024-09-18  6:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16 11:43 [PATCH 6.6 00/91] 6.6.52-rc1 review Greg Kroah-Hartman
2024-09-16 14:10 ` Takeshi Ogasawara
2024-09-16 16:29 ` Harshit Mogalapalli
2024-09-16 18:12 ` Peter Schneider
2024-09-17  9:56 ` Mark Brown
2024-09-17 10:30 ` Naresh Kamboju
2024-09-18  6:17   ` Greg Kroah-Hartman [this message]
2024-09-17 15:19 ` Jon Hunter
2024-09-17 21:44 ` Florian Fainelli
2024-09-17 22:35 ` Ron Economos
2024-09-18 10:03 ` Kexy Biscuit

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=2024091853-thickness-plexiglas-5e83@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=agordeev@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=anders.roxell@linaro.org \
    --cc=borntraeger@linux.ibm.com \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gor@linux.ibm.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