From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@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, slade@sladewatkins.com
Subject: [PATCH 5.15 0/5] 5.15.23-rc1 review
Date: Wed, 9 Feb 2022 20:14:25 +0100 [thread overview]
Message-ID: <20220209191249.980911721@linuxfoundation.org> (raw)
This is the start of the stable review cycle for the 5.15.23 release.
There are 5 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 Fri, 11 Feb 2022 19:12:41 +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.23-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
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Linux 5.15.23-rc1
Herbert Xu <herbert@gondor.apana.org.au>
crypto: api - Move cryptomgr soft dependency into algapi
Namjae Jeon <linkinjeon@kernel.org>
ksmbd: fix SMB 3.11 posix extension mount failure
Janis Schoetterl-Glausch <scgl@linux.ibm.com>
KVM: s390: Return error on SIDA memop on normal guest
Anshuman Khandual <anshuman.khandual@arm.com>
arm64: Add Cortex-A510 CPU part definition
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
moxart: fix potential use-after-free on remove path
-------------
Diffstat:
Makefile | 4 ++--
arch/arm64/include/asm/cputype.h | 2 ++
arch/s390/kvm/kvm-s390.c | 2 ++
crypto/algapi.c | 1 +
crypto/api.c | 1 -
drivers/mmc/host/moxart-mmc.c | 2 +-
fs/ksmbd/smb2pdu.c | 2 +-
7 files changed, 9 insertions(+), 5 deletions(-)
next reply other threads:[~2022-02-09 19:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 19:14 Greg Kroah-Hartman [this message]
2022-02-09 19:14 ` [PATCH 5.15 1/5] moxart: fix potential use-after-free on remove path Greg Kroah-Hartman
2022-02-09 19:14 ` [PATCH 5.15 2/5] arm64: Add Cortex-A510 CPU part definition Greg Kroah-Hartman
2022-02-09 19:14 ` [PATCH 5.15 3/5] KVM: s390: Return error on SIDA memop on normal guest Greg Kroah-Hartman
2022-02-09 19:14 ` [PATCH 5.15 4/5] ksmbd: fix SMB 3.11 posix extension mount failure Greg Kroah-Hartman
2022-02-09 19:14 ` [PATCH 5.15 5/5] crypto: api - Move cryptomgr soft dependency into algapi Greg Kroah-Hartman
2022-02-10 0:54 ` [PATCH 5.15 0/5] 5.15.23-rc1 review Fox Chen
2022-02-10 0:57 ` Shuah Khan
2022-02-10 7:47 ` Ron Economos
2022-02-10 10:49 ` Naresh Kamboju
2022-02-10 16:01 ` Sudip Mukherjee
2022-02-10 17:54 ` Florian Fainelli
2022-02-10 21:01 ` Guenter Roeck
2022-02-11 5:13 ` Bagas Sanjaya
2022-02-11 6:12 ` Slade Watkins
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=20220209191249.980911721@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.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=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=slade@sladewatkins.com \
--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