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, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.10 00/25] 6.10.6-rc2 review
Date: Sat, 17 Aug 2024 13:40:57 +0200 [thread overview]
Message-ID: <886e729c-d3fd-432f-8fce-6f6926b1fdbc@googlemail.com> (raw)
In-Reply-To: <20240816085226.888902473@linuxfoundation.org>
Am 16.08.2024 um 11:42 schrieb Greg Kroah-Hartman:
> This is the start of the stable review cycle for the 6.10.6 release.
> There are 25 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.
Now I'm a little bit confused. I saw you announced a new 6.10.6 RC and I wanted to
(re-)test it. Your subject says -rc2, but when I git fetch from the kernel.org
linux-stable-rc git repo (which I always do) what I get is -rc3 from today, however I have
not (yet) seen a mail from you announcing -rc3. Forgot to send that one out? Anyway, -rc3
is what I tested, and as I already reported for -rc1, it is fine on my machine, too.
I tested with running 4 QEMU/KVM virtual machines for an hour, and did not find any
problems, so:
Builds, boots and works on my 2-socket Ivy Bridge Xeon E5-2697 v2 server. No dmesg
oddities or regressions found.
Tested-by: Peter Schneider <pschneider1968@googlemail.com>
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
next prev parent reply other threads:[~2024-08-17 11:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 9:42 [PATCH 6.10 00/25] 6.10.6-rc2 review Greg Kroah-Hartman
2024-08-16 13:16 ` Mark Brown
2024-08-16 14:06 ` Markus Reichelt
2024-08-16 19:48 ` Jon Hunter
2024-08-16 20:25 ` Guenter Roeck
2024-08-16 20:35 ` Ron Economos
2024-08-17 4:00 ` Florian Fainelli
2024-08-17 5:35 ` Anders Roxell
2024-08-17 11:40 ` Peter Schneider [this message]
2024-08-18 8:54 ` Greg Kroah-Hartman
2024-08-17 16:24 ` Allen
-- strict thread matches above, loose matches on Subject: below --
2024-08-16 11:22 Ronald Warsow
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=886e729c-d3fd-432f-8fce-6f6926b1fdbc@googlemail.com \
--to=pschneider1968@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--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