From: "Slade Watkins" <slade@sladewatkins.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Guenter Roeck" <linux@roeck-us.net>,
shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, "Pavel Machek" <pavel@denx.de>,
"Jon Hunter" <jonathanh@nvidia.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Sudip Mukherjee" <sudipm.mukherjee@gmail.com>
Subject: Re: [PATCH 5.16 000/127] 5.16.8-rc2 review
Date: Tue, 08 Feb 2022 02:03:33 -0500 [thread overview]
Message-ID: <16bbddcb-d827-490a-ac80-cd5a75404d6f@www.fastmail.com> (raw)
In-Reply-To: <20220207133856.644483064@linuxfoundation.org>
On Mon, Feb 7, 2022, at 9:04 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.16.8 release.
> There are 127 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.
>
> Responses should be made by Wed, 09 Feb 2022 13:38:34 +0000.
> Anything received after that time might be too late.
Compiled and booted 5.16.8-rc2 on my x86_64 test system successfully without errors or regressions.
Tested-by: Slade Watkins <slade@sladewatkins.com>
Thanks,
Slade
next prev parent reply other threads:[~2022-02-08 7:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 14:04 [PATCH 5.16 000/127] 5.16.8-rc2 review Greg Kroah-Hartman
2022-02-07 19:55 ` Naresh Kamboju
2022-02-07 21:24 ` Shuah Khan
2022-02-07 22:22 ` Guenter Roeck
2022-02-07 22:34 ` Justin Forbes
2022-02-08 1:57 ` Zan Aziz
2022-02-08 2:47 ` Florian Fainelli
2022-02-08 7:03 ` Slade Watkins [this message]
2022-02-08 8:31 ` Bagas Sanjaya
2022-02-08 8:31 ` Jon Hunter
2022-02-08 9:02 ` Ron Economos
2022-02-08 10:30 ` Rudi Heitbaum
2022-02-08 11:34 ` Scott Bruce
2022-02-08 13:30 ` Fox Chen
2022-02-07 22:43 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=16bbddcb-d827-490a-ac80-cd5a75404d6f@www.fastmail.com \
--to=slade@sladewatkins.com \
--cc=akpm@linux-foundation.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=pavel@denx.de \
--cc=shuah@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).