From: Brett A C Sheffield <bacs@librecast.net>
To: gregkh@linuxfoundation.org
Cc: akpm@linux-foundation.org, brauner@kernel.org,
broonie@kernel.org, conor@kernel.org, f.fainelli@gmail.com,
hargar@microsoft.com, jack@suse.cz, jannh@google.com,
jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
linux@roeck-us.net, lkft-triage@lists.linaro.org,
patches@kernelci.org, patches@lists.linux.dev, pavel@denx.de,
rwarsow@gmx.de, shuah@kernel.org, srw@sladewatkins.net,
stable@vger.kernel.org, sudipm.mukherjee@gmail.com,
torvalds@linux-foundation.org, viro@zeniv.linux.org.uk,
Brett A C Sheffield <bacs@librecast.net>
Subject: Re: [PATCH 6.6 000/111] 6.6.99-rc2 review
Date: Thu, 17 Jul 2025 09:03:19 +0000 [thread overview]
Message-ID: <20250717090318.22708-2-bacs@librecast.net> (raw)
In-Reply-To: <20250715163542.059429276@linuxfoundation.org>
# Librecast Test Results
010/010 [ OK ] libmld
119/120 [FAIL] liblibrecast
CPU/kernel: Linux auntie 6.6.99-rc2-gefb1c34bdf5c #17 SMP PREEMPT_DYNAMIC Thu Jul 17 08:51:06 -00 2025 x86_64 AMD Ryzen 9 9950X 16-Core Processor AuthenticAMD GNU/Linux
There is one failing test with the 6.6 series kernels that I started digging into yesterday, but as this fails on *all* 6.6 kernels right back to 6.6.0 this isn't a regression in this RC so there is no reason to delay 6.6.99 for this. Works fine in 6.5.0 and in more recent kernels > 6.8. Will report this separately when I have more information.
Tested-by: Brett A C Sheffield <bacs@librecast.net>
prev parent reply other threads:[~2025-07-17 9:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 16:37 Greg Kroah-Hartman
2025-07-15 21:06 ` Miguel Ojeda
2025-07-16 9:22 ` Harshit Mogalapalli
2025-07-16 10:16 ` Jon Hunter
2025-07-16 10:40 ` Mark Brown
2025-07-16 11:07 ` Ron Economos
2025-07-16 11:44 ` Naresh Kamboju
2025-07-16 15:16 ` Peter Schneider
2025-07-16 18:45 ` Florian Fainelli
2025-07-17 9:03 ` Brett A C Sheffield [this message]
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=20250717090318.22708-2-bacs@librecast.net \
--to=bacs@librecast.net \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jack@suse.cz \
--cc=jannh@google.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 \
--cc=viro@zeniv.linux.org.uk \
/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®