From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
ben.hutchings@codethink.co.uk, lkft-triage@lists.linaro.org,
stable@vger.kernel.org
Subject: Re: [PATCH 5.5 000/190] 5.5.9-rc2 review
Date: Wed, 11 Mar 2020 19:27:26 +0100 [thread overview]
Message-ID: <20200311182726.GA4021147@kroah.com> (raw)
In-Reply-To: <20200311181532.692464938@linuxfoundation.org>
On Wed, Mar 11, 2020 at 07:19:11PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.5.9 release.
> There are 190 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, 13 Mar 2020 18:14:21 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.5.9-rc2.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.5.y
> and the diffstat can be found below.
I got the request from some of the teams doing "automatic testing" that
it was hard to trigger their test runs when I did a -rc2 and -rc3 and so
on, as I was just responding to them "by hand".
So I tweaked my scripts a bit and now will send out these types of
automated emails for when I push out a new -rc for the stable releases.
For those that didn't know, there are a bunch of "X-KernelTest-" headers
in these emails, that should be enough to help trigger just about any
type of test systems out there. If there's any info missing there, that
will help you out, please let me know.
thanks,
greg k-h
next prev parent reply other threads:[~2020-03-11 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 18:19 [PATCH 5.5 000/190] 5.5.9-rc2 review Greg Kroah-Hartman
2020-03-11 18:27 ` Greg Kroah-Hartman [this message]
2020-03-11 21:40 ` Guenter Roeck
2020-03-12 6:21 ` Greg Kroah-Hartman
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=20200311182726.GA4021147@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--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).