From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: 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
Subject: Re: [PATCH 6.7 000/353] 6.7.4-rc1 review
Date: Sat, 3 Feb 2024 11:36:28 +0100 [thread overview]
Message-ID: <e07488c7-8375-5d03-d2b6-eba2a9769684@applied-asynchrony.com> (raw)
In-Reply-To: <9fa210ec-1086-615e-b972-f28a74df7b49@applied-asynchrony.com>
On 2024-02-03 11:18, Holger Hoffstätte wrote:
> On 2024-02-03 05:01, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 6.7.4 release.
>> There are 353 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.
>
> On my Zen2-based Thinkpad I now get the trace below on boot; this never
> happened before. The boot continues and the system seems usable.
..except for the part where reboot hangs, but whatever.
In any case reverting the patch makes the trace disappear.
-h
next prev parent reply other threads:[~2024-02-03 10:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 4:01 Greg Kroah-Hartman
2024-02-03 7:02 ` Daniel Díaz
2024-02-03 16:01 ` Greg Kroah-Hartman
2024-02-03 10:18 ` Holger Hoffstätte
2024-02-03 10:36 ` Holger Hoffstätte [this message]
2024-02-03 15:42 ` Greg Kroah-Hartman
2024-02-03 17:43 ` Florian Fainelli
2024-02-03 13:39 Ronald Warsow
2024-02-03 14:46 ` Greg Kroah-Hartman
2024-02-03 16:23 ` Ronald Warsow
2024-02-03 16:28 ` Greg Kroah-Hartman
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=e07488c7-8375-5d03-d2b6-eba2a9769684@applied-asynchrony.com \
--to=holger@applied-asynchrony.com \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®