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, shuahkh@osg.samsung.com,
patches@kernelci.org, ben.hutchings@codethink.co.uk,
stable@vger.kernel.org
Subject: Re: [PATCH 4.13 0/2] 4.13.7-stable review
Date: Fri, 13 Oct 2017 14:54:17 +0200 [thread overview]
Message-ID: <20171013125417.GD14078@kroah.com> (raw)
In-Reply-To: <74063f62-cdcc-eb51-4d0e-97b9e7e45f39@roeck-us.net>
On Fri, Oct 13, 2017 at 05:41:02AM -0700, Guenter Roeck wrote:
> On 10/12/2017 02:26 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.13.7 release.
> > There are 2 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 Sat Oct 14 21:25:27 UTC 2017.
> > Anything received after that time might be too late.
> >
>
> Build results:
> total: 145 pass: 145 fail: 0
> Qemu test results:
> total: 123 pass: 123 fail: 0
>
> Details are available at http://kerneltests.org/builders.
Wonderful, thanks for testing and letting me know.
greg k-h
prev parent reply other threads:[~2017-10-13 12:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 21:26 [PATCH 4.13 0/2] 4.13.7-stable review Greg Kroah-Hartman
2017-10-12 21:26 ` [PATCH 4.13 1/2] watchdog: Revert "iTCO_wdt: all versions count down twice" Greg Kroah-Hartman
2017-10-12 21:26 ` [PATCH 4.13 2/2] waitid(): Add missing access_ok() checks Greg Kroah-Hartman
2017-10-13 23:55 ` David Daney
2017-10-12 23:45 ` [PATCH 4.13 0/2] 4.13.7-stable review Shuah Khan
2017-10-13 0:09 ` John Stultz
2017-10-13 14:05 ` Shuah Khan
2017-10-13 15:12 ` Shuah Khan
2017-10-13 17:00 ` John Stultz
2017-10-13 5:41 ` Greg Kroah-Hartman
2017-10-13 12:41 ` Guenter Roeck
2017-10-13 12:54 ` Greg Kroah-Hartman [this message]
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=20171013125417.GD14078@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=patches@kernelci.org \
--cc=shuahkh@osg.samsung.com \
--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).