From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Daniel Díaz" <daniel.diaz@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
Subject: Re: [PATCH 5.15 00/37] 5.15.115-rc2 review
Date: Sat, 3 Jun 2023 16:36:04 +0200 [thread overview]
Message-ID: <2023060350-mountable-deploy-09bd@gregkh> (raw)
In-Reply-To: <CAEUSe7-qcYwBbeFGKAOvf-rPMdgAMfE6t42Urnhjam9nWN-gFg@mail.gmail.com>
On Thu, Jun 01, 2023 at 10:17:48PM -0600, Daniel Díaz wrote:
> Hello!
>
> On Thu, 1 Jun 2023 at 08:36, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 5.15.115 release.
> > There are 37 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, 03 Jun 2023 14:33:22 +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.115-rc2.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
>
> Build failures on System/390:
> -----8<-----
> /builds/linux/arch/s390/kernel/uv.c: In function
> 'should_export_before_import':
> /builds/linux/arch/s390/kernel/uv.c:204:40: error: 'mm_context_t'
> has no member named 'protected_count'
> 204 | return atomic_read(&mm->context.protected_count) > 1;
> | ^
> /builds/linux/arch/s390/kernel/uv.c:205:1: error: control reaches
> end of non-void function [-Werror=return-type]
> 205 | }
> | ^
> ----->8-----
>
> That's with defconfig and GCC-8, GCC-12, Clang-16.
Thanks, I've dropped the broken patches now and will push out a -rc3.
greg k-h
next prev parent reply other threads:[~2023-06-03 14:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 14:36 [PATCH 5.15 00/37] 5.15.115-rc2 review Greg Kroah-Hartman
2023-06-01 16:53 ` Florian Fainelli
2023-06-01 20:42 ` Shuah Khan
2023-06-02 4:17 ` Daniel Díaz
2023-06-03 14:36 ` Greg Kroah-Hartman [this message]
2023-06-02 8:36 ` Ron Economos
2023-06-02 8:45 ` Jon Hunter
2023-06-02 9:01 ` Bagas Sanjaya
2023-06-02 12:07 ` Sudip Mukherjee
2023-06-02 12:33 ` Guenter Roeck
2023-06-03 14:36 ` Greg Kroah-Hartman
2023-06-02 15:40 ` Harshit Mogalapalli
2023-06-02 22:35 ` Guenter Roeck
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=2023060350-mountable-deploy-09bd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=daniel.diaz@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=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