From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
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, slade@sladewatkins.com
Subject: Re: [PATCH 5.17 0000/1123] 5.17.2-rc2 review
Date: Thu, 7 Apr 2022 10:44:40 -0700 [thread overview]
Message-ID: <20220407174440.GC1827081@roeck-us.net> (raw)
In-Reply-To: <20220406133122.897434068@linuxfoundation.org>
On Wed, Apr 06, 2022 at 03:44:54PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.17.2 release.
> There are 1123 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 Fri, 08 Apr 2022 13:27:53 +0000.
> Anything received after that time might be too late.
>
Build results:
total: 155 pass: 155 fail: 0
Qemu test results:
total: 488 pass: 488 fail: 0
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Guenter
next prev parent reply other threads:[~2022-04-07 17:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 13:44 [PATCH 5.17 0000/1123] 5.17.2-rc2 review Greg Kroah-Hartman
2022-04-06 19:14 ` Jon Hunter
2022-04-06 19:23 ` Justin Forbes
2022-04-06 19:58 ` Fox Chen
2022-04-06 22:48 ` Shuah Khan
2022-04-06 23:52 ` Florian Fainelli
2022-04-07 0:37 ` Ron Economos
2022-04-07 8:35 ` Jiri Slaby
2022-04-07 10:57 ` Naresh Kamboju
2022-04-07 11:45 ` Bagas Sanjaya
2022-04-08 8:07 ` Bagas Sanjaya
2022-04-11 14:53 ` Geert Uytterhoeven
2022-04-07 17:44 ` Guenter Roeck [this message]
2022-04-07 22:11 ` Sebastian Döring
2022-04-07 23:02 ` Rudi Heitbaum
-- strict thread matches above, loose matches on Subject: below --
2022-04-06 22:52 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=20220407174440.GC1827081@roeck-us.net \
--to=linux@roeck-us.net \
--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=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=slade@sladewatkins.com \
--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