From: Shuah Khan <shuahkh@osg.samsung.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah.kh@samsung.com, stable@vger.kernel.org
Subject: Re: [PATCH 3.10 00/14] 3.10.84-stable review
Date: Wed, 08 Jul 2015 10:33:11 -0600 [thread overview]
Message-ID: <559D50C7.3010801@osg.samsung.com> (raw)
In-Reply-To: <20150708073102.284623533@linuxfoundation.org>
On 07/08/2015 01:31 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.84 release.
> There are 14 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 Jul 10 07:30:40 UTC 2015.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.10.84-rc1.gz
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah
--
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978
next prev parent reply other threads:[~2015-07-08 16:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 7:31 [PATCH 3.10 00/14] 3.10.84-stable review Greg Kroah-Hartman
2015-07-08 7:31 ` [PATCH 3.10 01/14] sparc: Use GFP_ATOMIC in ldc_alloc_exp_dring() as it can be called in softirq context Greg Kroah-Hartman
2015-07-08 7:31 ` [PATCH 3.10 02/14] bridge: fix multicast router rlist endless loop Greg Kroah-Hartman
2015-07-08 7:31 ` [PATCH 3.10 03/14] bridge: fix br_stp_set_bridge_priority race conditions Greg Kroah-Hartman
2015-07-08 7:31 ` [PATCH 3.10 04/14] packet: read num_members once in packet_rcv_fanout() Greg Kroah-Hartman
2015-07-08 7:31 ` [PATCH 3.10 05/14] packet: avoid out of bounds read in round robin fanout Greg Kroah-Hartman
2015-07-08 7:31 ` [PATCH 3.10 06/14] sctp: Fix race between OOTB responce and route removal Greg Kroah-Hartman
2015-07-08 7:31 ` [PATCH 3.10 07/14] crypto: talitos - avoid memleak in talitos_alg_alloc() Greg Kroah-Hartman
2015-07-08 7:31 ` [PATCH 3.10 08/14] Revert "crypto: talitos - convert to use be16_add_cpu()" Greg Kroah-Hartman
2015-07-08 7:31 ` [PATCH 3.10 09/14] arm: KVM: force execution of HCPTR access on VM exit Greg Kroah-Hartman
2015-07-08 7:31 ` [PATCH 3.10 10/14] powerpc/perf: Fix book3s kernel to userspace backtraces Greg Kroah-Hartman
2015-07-08 7:31 ` [PATCH 3.10 11/14] x86/PCI: Use host bridge _CRS info on Foxconn K8M890-8237A Greg Kroah-Hartman
2015-07-08 7:31 ` [PATCH 3.10 12/14] MIPS: Fix KVM guest fixmap address Greg Kroah-Hartman
2015-07-08 7:31 ` [PATCH 3.10 14/14] fs: Fix S_NOSEC handling Greg Kroah-Hartman
2015-07-08 14:06 ` [PATCH 3.10 00/14] 3.10.84-stable review Guenter Roeck
2015-07-08 14:42 ` Sudip Mukherjee
2015-07-08 16:33 ` Shuah Khan [this message]
2015-07-09 18:13 ` Kevin Hilman
2015-07-10 17:34 ` Greg Kroah-Hartman
2015-07-10 18:51 ` Kevin Hilman
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=559D50C7.3010801@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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 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).