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.kh@samsung.com,
patches@kernelci.org, ben.hutchings@codethink.co.uk,
stable@vger.kernel.org
Subject: Re: [PATCH 4.8 00/10] 4.8.1-stable review
Date: Fri, 7 Oct 2016 06:05:36 +0200 [thread overview]
Message-ID: <20161007040536.GG17183@kroah.com> (raw)
In-Reply-To: <20161006185101.GC11915@roeck-us.net>
On Thu, Oct 06, 2016 at 11:51:01AM -0700, Guenter Roeck wrote:
> On Thu, Oct 06, 2016 at 10:18:23AM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.8.1 release.
> > There are 10 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 8 07:47:33 UTC 2016.
> > Anything received after that time might be too late.
> >
>
> Build results:
> total: 149 pass: 149 fail: 0
> Qemu test results:
> total: 108 pass: 108 fail: 0
>
> Details are available at http://kerneltests.org/builders.
Great, thanks for testing all of these and letting me know.
greg k-h
next prev parent reply other threads:[~2016-10-07 4:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161006081902uscas1p14629784f61bb4f76ecbc7f7298e4eeb3@uscas1p1.samsung.com>
2016-10-06 8:18 ` [PATCH 4.8 00/10] 4.8.1-stable review Greg Kroah-Hartman
2016-10-06 8:18 ` [PATCH 4.8 01/10] arm64: debug: avoid resetting stepping state machine when TIF_SINGLESTEP Greg Kroah-Hartman
2016-10-06 8:18 ` [PATCH 4.8 02/10] Using BUG_ON() as an assert() is _never_ acceptable Greg Kroah-Hartman
2016-10-06 8:18 ` [PATCH 4.8 03/10] usb: misc: legousbtower: Fix NULL pointer deference Greg Kroah-Hartman
2016-10-06 8:18 ` [PATCH 4.8 04/10] Staging: fbtft: Fix bug in fbtft-core Greg Kroah-Hartman
2016-10-06 8:18 ` [PATCH 4.8 05/10] usb: usbip: vudc: fix left shift overflow Greg Kroah-Hartman
2016-10-06 8:18 ` [PATCH 4.8 06/10] USB: serial: cp210x: Add ID for a Juniper console Greg Kroah-Hartman
2016-10-06 8:18 ` [PATCH 4.8 07/10] Revert "usbtmc: convert to devm_kzalloc" Greg Kroah-Hartman
2016-10-06 8:18 ` [PATCH 4.8 08/10] ALSA: hda - Adding one more ALC255 pin definition for headset problem Greg Kroah-Hartman
2016-10-06 8:18 ` [PATCH 4.8 09/10] ALSA: hda - Fix headset mic detection problem for several Dell laptops Greg Kroah-Hartman
2016-10-06 8:18 ` [PATCH 4.8 10/10] ALSA: hda - Add the top speaker pin config for HP Spectre x360 Greg Kroah-Hartman
2016-10-06 18:51 ` [PATCH 4.8 00/10] 4.8.1-stable review Guenter Roeck
2016-10-07 4:05 ` Greg Kroah-Hartman [this message]
2016-10-06 19:56 ` Shuah Khan
2016-10-07 4:05 ` Greg Kroah-Hartman
[not found] ` <57f820fc.4398c20a.3305b.cf51@mx.google.com>
2016-10-08 14:03 ` Greg Kroah-Hartman
2016-10-08 16:11 ` Kevin Hilman
2016-10-08 17:22 ` Guenter Roeck
2016-10-10 9:38 ` Mark Brown
2016-10-10 12:54 ` Guenter Roeck
2016-10-10 19:11 ` Mark Brown
2016-10-10 19:47 ` Guenter Roeck
2016-10-11 7:24 ` Mark Brown
2016-10-11 10:19 ` Mark Brown
2016-10-11 13:37 ` 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=20161007040536.GG17183@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=shuah.kh@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 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.