From: Brett A C Sheffield <bacs@librecast.net>
To: gregkh@linuxfoundation.org
Cc: stable@vger.kernel.org, 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,
achill@achill.org, Brett A C Sheffield <bacs@librecast.net>
Subject: Re: [PATCH 6.16 000/183] 6.16.6-rc1 review
Date: Mon, 8 Sep 2025 09:25:34 +0000 [thread overview]
Message-ID: <20250908092533.22608-2-bacs@librecast.net> (raw)
In-Reply-To: <20250907195615.802693401@linuxfoundation.org>
# Librecast Test Results
010/010 [ OK ] libmld
120/120 [ OK ] liblibrecast
CPU/kernel: Linux auntie 6.16.6-rc1-g665877a17a1b #62 SMP PREEMPT_DYNAMIC Mon Sep 8 06:39:13 -00 2025 x86_64 AMD Ryzen 9 9950X 16-Core Processor AuthenticAMD GNU/Linux
Tested-by: Brett A C Sheffield <bacs@librecast.net>
next prev parent reply other threads:[~2025-09-08 9:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 19:57 [PATCH 6.16 000/183] 6.16.6-rc1 review Greg Kroah-Hartman
2025-09-08 1:49 ` Ronald Warsow
2025-09-08 3:41 ` Takeshi Ogasawara
2025-09-08 3:50 ` Florian Fainelli
2025-09-08 7:38 ` Achill Gilgenast
2025-09-08 9:25 ` Brett A C Sheffield [this message]
2025-09-08 11:31 ` Miguel Ojeda
2025-09-08 11:58 ` Peter Schneider
2025-09-08 15:02 ` Jon Hunter
2025-09-08 15:50 ` Markus Reichelt
2025-09-08 18:20 ` Justin Forbes
2025-09-08 22:35 ` Shuah Khan
2025-09-09 4:57 ` Dileep malepu
2025-09-09 5:47 ` Ron Economos
2025-09-09 8:14 ` Naresh Kamboju
2025-09-09 11:21 ` Mark Brown
2025-09-09 17:26 ` Christian Heusel
2025-09-09 17:48 ` Hardik Garg
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=20250908092533.22608-2-bacs@librecast.net \
--to=bacs@librecast.net \
--cc=achill@achill.org \
--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