public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
	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,
	Arnd Bergmann <arnd@arndb.de>,
	Anders Roxell <anders.roxell@linaro.org>
Subject: Re: [PATCH 5.15 000/144] 5.15.163-rc1 review
Date: Wed, 17 Jul 2024 08:21:32 +0200	[thread overview]
Message-ID: <2024071705-fable-implosive-5e34@gregkh> (raw)
In-Reply-To: <2024071743-anyhow-legroom-1d54@gregkh>

On Wed, Jul 17, 2024 at 08:15:08AM +0200, Greg Kroah-Hartman wrote:
> On Tue, Jul 16, 2024 at 03:45:33PM -0500, Dan Carpenter wrote:
> > On Wed, Jul 17, 2024 at 01:49:12AM +0530, Naresh Kamboju wrote:
> > > On Tue, 16 Jul 2024 at 21:37, Greg Kroah-Hartman
> > > <gregkh@linuxfoundation.org> wrote:
> > > >
> > > > This is the start of the stable review cycle for the 5.15.163 release.
> > > > There are 144 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, 18 Jul 2024 15:27:21 +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.163-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 s390 builds failed on stable-rc 5.15.163-rc1 review due to following build
> > > warnings / errors.
> > > 
> > > First time seen on stable-rc 5.15 branch.
> > > 
> > >   GOOD: ba1631e1a5cc ("Linux 5.15.162-rc1")
> > >   BAD:  b9a293390e62 ("Linux 5.15.163-rc1")
> > > 
> > > * s390, build
> > >   - clang-18-allnoconfig
> > >   - clang-18-defconfig
> > >   - clang-18-tinyconfig
> > >   - clang-nightly-allnoconfig
> > >   - clang-nightly-defconfig
> > >   - clang-nightly-tinyconfig
> > >   - gcc-12-allnoconfig
> > >   - gcc-12-defconfig
> > >   - gcc-12-tinyconfig
> > >   - gcc-8-allnoconfig
> > >   - gcc-8-defconfig-fe40093d
> > >   - gcc-8-tinyconfig
> > > 
> > > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> > > 
> > > Build regressions:
> > > --------
> > > arch/s390/include/asm/processor.h:253:11: error: expected ';' at end
> > > of declaration
> > >   253 |         psw_t psw __uninitialized;
> > >       |                  ^
> > >       |                  ;
> > > 1 error generated.
> > 
> > Need to cherry-pick commit fd7eea27a3ae ("Compiler Attributes: Add __uninitialized macro")
> 
> Thanks, as this keeps coming back, I'll go add this commit now to all
> branches and push out -rc2 releases in a few hours.

Nope, not doing this for 4.19.y, that's going to turn into too much of a
mess there.  I'll just drop the offending commit from that branch for
now, thanks.

greg k-h

  reply	other threads:[~2024-07-17  6:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-16 15:31 [PATCH 5.15 000/144] 5.15.163-rc1 review Greg Kroah-Hartman
2024-07-16 18:23 ` Florian Fainelli
2024-07-16 18:39 ` SeongJae Park
2024-07-16 19:43 ` Mark Brown
2024-07-16 20:19 ` Naresh Kamboju
2024-07-16 20:45   ` Dan Carpenter
2024-07-17  6:15     ` Greg Kroah-Hartman
2024-07-17  6:21       ` Greg Kroah-Hartman [this message]
2024-07-17 15:53 ` Shuah Khan
2024-07-17 16:56 ` Allen

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=2024071705-fable-implosive-5e34@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