From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Holger Kiehl <Holger.Kiehl@dwd.de>
Cc: 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,
stable@vger.kernel.org
Subject: Re: [PATCH 5.15 000/923] 5.15.3-rc3 review
Date: Thu, 18 Nov 2021 09:14:26 +0100 [thread overview]
Message-ID: <YZYLYlvdfi9ddToA@kroah.com> (raw)
In-Reply-To: <413ef3-c782-be14-da3-da86ed14a210@diagnostix.dwd.de>
On Wed, Nov 17, 2021 at 08:25:12PM +0000, Holger Kiehl wrote:
> Hello,
>
> On Wed, 17 Nov 2021, Greg Kroah-Hartman wrote:
>
> > This is the start of the stable review cycle for the 5.15.3 release.
> > There are 923 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, 19 Nov 2021 10:14:52 +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.3-rc3.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.
> >
> On a Deskmini X300 with a AMD APU 5700G this does not boot (rc1+rc2 also
> do not boot). As Scott Bruce already noticed, if one removes
> c3fc9d9e8f2dc518a8ce3c77f833a11b47865944 "x86: Fix __get_wchan() for
> !STACKTRACE" it boots.
Now dropped, thanks.
greg k-h
next prev parent reply other threads:[~2021-11-18 8:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 10:19 [PATCH 5.15 000/923] 5.15.3-rc3 review Greg Kroah-Hartman
2021-11-17 13:37 ` Fox Chen
2021-11-17 14:13 ` Guenter Roeck
2021-11-17 14:43 ` Greg Kroah-Hartman
2021-11-17 14:54 ` Guenter Roeck
2021-11-17 17:34 ` Jon Hunter
2021-11-17 18:51 ` Florian Fainelli
2021-11-17 20:25 ` Holger Kiehl
2021-11-18 8:14 ` Greg Kroah-Hartman [this message]
2021-11-18 14:08 ` Holger Kiehl
2021-11-18 17:08 ` Greg Kroah-Hartman
2021-11-17 20:35 ` Guenter Roeck
2021-11-17 21:32 ` Justin Forbes
2021-11-17 23:32 ` Holger Hoffstätte
2021-11-17 23:50 ` Linus Torvalds
2021-11-18 0:16 ` Kees Cook
2021-11-18 6:26 ` Guenter Roeck
2021-11-18 8:14 ` Greg Kroah-Hartman
2021-11-18 8:12 ` Greg Kroah-Hartman
2021-11-18 17:17 ` Kees Cook
2021-11-18 8:06 ` Peter Zijlstra
2021-11-18 8:18 ` Peter Zijlstra
2021-11-18 9:39 ` Peter Zijlstra
2021-11-18 10:12 ` Peter Zijlstra
2021-11-18 12:11 ` Peter Zijlstra
2021-11-19 2:04 ` Josh Poimboeuf
2021-11-19 9:29 ` [PATCH] x86: Pin task-stack in __get_wchan() Peter Zijlstra
2021-11-19 10:02 ` Qi Zheng
2021-11-19 10:22 ` Peter Zijlstra
2021-11-19 10:26 ` Qi Zheng
2021-11-19 18:16 ` Linus Torvalds
2021-11-19 18:35 ` Josh Poimboeuf
2021-11-22 9:32 ` Peter Zijlstra
2021-11-22 16:14 ` Josh Poimboeuf
2021-11-18 5:45 ` [PATCH 5.15 000/923] 5.15.3-rc3 review Naresh Kamboju
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=YZYLYlvdfi9ddToA@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Holger.Kiehl@dwd.de \
--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=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).