From: Peter Schneider <pschneider1968@googlemail.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, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.6 000/222] 6.6.70-rc1 review
Date: Tue, 7 Jan 2025 02:16:51 +0100 [thread overview]
Message-ID: <e335fd7b-1a22-4ce1-b77b-ff74cd311e01@googlemail.com> (raw)
In-Reply-To: <896ab5a8-e86b-4176-812f-9111b44df90a@googlemail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1457 bytes --]
Am 07.01.2025 um 01:36 schrieb Peter Schneider:
> Am 06.01.2025 um 16:13 schrieb Greg Kroah-Hartman:
>> This is the start of the stable review cycle for the 6.6.70 release.
>> There are 222 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.
>
> 6.6.70-rc1 builds, boots and seems to work on my 2-socket Ivy Bridge Xeon E5-2697 v2
> server, but I see a scary looking dmesg warning, right after booting. As it is currently
> running, I will try building 6.12.9-rc with it, and see how that goes. The dmesg warnings
> I see look similar to that already reported by Miguel Ojeda.
[...]
So running 6.6.70-rc1, despite the above mentioned initial warning message, I could build
6.12.9-rc1 just fine with it. It took the usual ~20 minutes, and no more dmesgs warning
have been added.
Beste Grüße,
Peter Schneider
--
Climb the mountain not to plant your flag, but to embrace the challenge,
enjoy the air and behold the view. Climb it so you can see the world,
not so the world can see you. -- David McCullough Jr.
OpenPGP: 0xA3828BD796CCE11A8CADE8866E3A92C92C3FF244
Download: https://www.peters-netzplatz.de/download/pschneider1968_pub.asc
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@googlemail.com
https://keys.mailvelope.com/pks/lookup?op=get&search=pschneider1968@gmail.com
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2025-01-07 1:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 15:13 Greg Kroah-Hartman
2025-01-06 19:00 ` Naresh Kamboju
2025-01-09 11:39 ` Greg Kroah-Hartman
2025-01-06 20:04 ` Miguel Ojeda
2025-01-06 20:13 ` Florian Fainelli
2025-01-07 0:36 ` Peter Schneider
2025-01-07 1:16 ` Peter Schneider [this message]
2025-01-07 0:54 ` SeongJae Park
2025-01-07 7:03 ` Ron Economos
2025-01-07 10:24 ` Naresh Kamboju
2025-01-07 13:01 ` Mike Rapoport
2025-01-09 11:52 ` Greg Kroah-Hartman
2025-01-07 12:33 ` Mark Brown
2025-01-07 12:44 ` Jon Hunter
2025-01-07 21:20 ` [PATCH 6.6] " Hardik Garg
2025-01-07 23:15 ` [PATCH 6.6 000/222] " Shuah Khan
2025-01-08 12:27 ` Muhammad Usama Anjum
2025-01-08 14:12 ` Harshit Mogalapalli
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=e335fd7b-1a22-4ce1-b77b-ff74cd311e01@googlemail.com \
--to=pschneider1968@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.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
Powered by JetHome