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.15 000/251] 5.15.47-rc2 review
Date: Tue, 14 Jun 2022 08:36:07 -0700 [thread overview]
Message-ID: <20220614153607.GB3088490@roeck-us.net> (raw)
In-Reply-To: <20220613181847.216528857@linuxfoundation.org>
On Mon, Jun 13, 2022 at 08:19:49PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.47 release.
> There are 251 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, 15 Jun 2022 18:18:03 +0000.
> Anything received after that time might be too late.
>
Build results:
total: 159 pass: 159 fail: 0
Qemu test results:
total: 488 pass: 488 fail: 0
Tested-by: Guenter Roeck <linux@roeck-us.net>
Guenter
next prev parent reply other threads:[~2022-06-14 15:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 18:19 Greg Kroah-Hartman
2022-06-13 21:00 ` Florian Fainelli
2022-06-14 3:06 ` Shuah Khan
2022-06-14 3:32 ` Fox Chen
2022-06-14 10:21 ` Sudip Mukherjee
2022-06-14 15:36 ` Guenter Roeck [this message]
2022-06-14 16:58 ` Allen Pais
2022-06-14 17:08 ` Guenter Roeck
2022-06-14 17:12 ` Greg Kroah-Hartman
2022-06-14 19:18 ` Naresh Kamboju
2022-06-14 17:47 Thomas Backlund
2022-06-14 18:51 ` Linus Torvalds
2022-06-14 19:00 ` Linus Torvalds
2022-06-15 11:00 ` Jan Kara
2022-06-15 13:38 ` Jan Kara
2022-06-15 18:00 ` Guenter Roeck
2022-06-15 21:47 ` Jan Kara
2022-06-16 8:04 ` Suzuki K Poulose
2022-06-15 10:04 ` Jan Kara
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=20220614153607.GB3088490@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
all inboxes | Powered by JetHome®