From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, shuah@kernel.org,
patches@kernelci.org, ben.hutchings@codethink.co.uk,
lkft-triage@lists.linaro.org, stable@vger.kernel.org
Subject: Re: [PATCH 4.14 0/1] 4.14.131-stable review
Date: Thu, 27 Jun 2019 08:11:32 +0800 [thread overview]
Message-ID: <20190627001132.GD527@kroah.com> (raw)
In-Reply-To: <20190626173613.GB2530@roeck-us.net>
On Wed, Jun 26, 2019 at 10:36:13AM -0700, Guenter Roeck wrote:
> On Wed, Jun 26, 2019 at 04:45:20PM +0800, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.131 release.
> > There are 1 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 28 Jun 2019 08:35:42 AM UTC.
> > Anything received after that time might be too late.
> >
>
> Build results:
> total: 172 pass: 172 fail: 0
> Qemu test results:
> total: 346 pass: 346 fail: 0
Wonderful, thanks for testing these and letting me know.
greg k-h
next prev parent reply other threads:[~2019-06-27 0:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 8:45 [PATCH 4.14 0/1] 4.14.131-stable review Greg Kroah-Hartman
2019-06-26 8:45 ` [PATCH 4.14 1/1] tcp: refine memory limit test in tcp_fragment() Greg Kroah-Hartman
2019-06-26 13:51 ` [PATCH 4.14 0/1] 4.14.131-stable review kernelci.org bot
2019-06-26 14:45 ` Naresh Kamboju
2019-06-27 0:12 ` Greg Kroah-Hartman
2019-06-26 17:36 ` Guenter Roeck
2019-06-27 0:11 ` Greg Kroah-Hartman [this message]
2019-06-26 22:32 ` shuah
2019-06-27 0:11 ` Greg Kroah-Hartman
2019-06-27 8:38 ` Jon Hunter
2019-06-28 8:26 ` Kelsey
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=20190627001132.GD527@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).