From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
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.16 000/184] 5.16.13-rc2 review
Date: Tue, 8 Mar 2022 19:57:53 +0100 [thread overview]
Message-ID: <YienMYvdhGPCcPSv@kroah.com> (raw)
In-Reply-To: <20220308185219.GA3686655@roeck-us.net>
On Tue, Mar 08, 2022 at 10:52:19AM -0800, Guenter Roeck wrote:
> On Mon, Mar 07, 2022 at 05:28:30PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.16.13 release.
> > There are 184 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 Mar 2022 16:21:20 +0000.
> > Anything received after that time might be too late.
> >
>
> Your cycles are getting too short for my test system to provide results
> in time. It gets overwhelmed, especially when there are updates affecting
> all stable branches which trigger a complete rebuild of all those branches.
Sorry, but this one had to go out a bit sooner for reasons I don't want
to speculate about :)
Anyway, I checked your builders, and they all looked ok except the 5.15
tree, which I know is broken on MIPS right now.
thanks,
greg k-h
next prev parent reply other threads:[~2022-03-08 18:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 16:28 [PATCH 5.16 000/184] 5.16.13-rc2 review Greg Kroah-Hartman
2022-03-07 19:57 ` Florian Fainelli
2022-03-07 23:49 ` Shuah Khan
2022-03-08 0:25 ` Fox Chen
2022-03-08 7:33 ` Naresh Kamboju
2022-03-08 10:12 ` Jon Hunter
2022-03-08 12:46 ` Rudi Heitbaum
2022-03-08 13:35 ` Justin Forbes
2022-03-08 13:55 ` Bagas Sanjaya
2022-03-08 17:02 ` Ron Economos
2022-03-08 18:52 ` Guenter Roeck
2022-03-08 18:57 ` Greg Kroah-Hartman [this message]
2022-03-08 20:49 ` Guenter Roeck
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=YienMYvdhGPCcPSv@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.