From: Guenter Roeck <linux@roeck-us.net>
To: Jiri Slaby <jslaby@suse.cz>, stable@vger.kernel.org
Cc: shuah.kh@samsung.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3.12 0/5] 3.12.66-stable review
Date: Thu, 20 Oct 2016 04:34:40 -0700 [thread overview]
Message-ID: <5fd7ccfc-e9d2-7b44-d170-3ad2ac719d70@roeck-us.net> (raw)
In-Reply-To: <cover.1476953088.git.jslaby@suse.cz>
On 10/20/2016 01:44 AM, Jiri Slaby wrote:
> This is the start of the stable review cycle for the 3.12.66 release.
> There are 5 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 Mon Oct 24 10:44:48 CEST 2016.
> Anything received after that time might be too late.
>
Build results:
total: 128 pass: 128 fail: 0
Qemu test results:
total: 85 pass: 85 fail: 0
Details are available at http://kerneltests.org/builders.
Guenter
next prev parent reply other threads:[~2016-10-20 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161020084517uscas1p26fd04e58e01da2bfc2bca6856d3e8827@uscas1p2.samsung.com>
2016-10-20 8:44 ` Jiri Slaby
2016-10-20 8:45 ` [PATCH 3.12 1/5] dm: fix AB-BA deadlock in __dm_destroy() Jiri Slaby
2016-10-20 8:51 ` Jiri Slaby
2016-10-20 8:45 ` [PATCH 3.12 2/5] ratelimit: fix bug in time interval by resetting right begin time Jiri Slaby
2016-10-20 8:45 ` [PATCH 3.12 3/5] brcmfmac: avoid potential stack overflow in brcmf_cfg80211_start_ap() Jiri Slaby
2016-10-20 8:45 ` [PATCH 3.12 4/5] x86/build: Build compressed x86 kernels as PIE Jiri Slaby
2016-10-20 8:45 ` [PATCH 3.12 5/5] mm: remove gup_flags FOLL_WRITE games from __get_user_pages() Jiri Slaby
2016-10-20 11:34 ` Guenter Roeck [this message]
2016-10-21 6:08 ` [PATCH 3.12 0/5] 3.12.66-stable review Jiri Slaby
2016-10-20 14:29 ` Shuah Khan
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=5fd7ccfc-e9d2-7b44-d170-3ad2ac719d70@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=shuah.kh@samsung.com \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®