From: Kevin Hilman <khilman@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, 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: Fri, 10 Jul 2015 11:51:42 -0700 [thread overview]
Message-ID: <7hfv4vals1.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20150710173447.GG10580@kroah.com> (Greg Kroah-Hartman's message of "Fri, 10 Jul 2015 10:34:47 -0700")
Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
> On Thu, Jul 09, 2015 at 11:13:36AM -0700, Kevin Hilman wrote:
>> Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
>>
>> > 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.
>>
>> Boot test results from kernelci.org below. Note that the boot failures
>> found are not new failures in this version, so should not block release.
>
> Anything we should be backporting to resolve those failures? Or does
> this kernel version just not really matter for those platforms?
We're looking into the failures now, and will submit any backports
needed. However, I think these remaining failures are just things that
never worked in v3.10, and we're finding as we add platforms to
kernelci.org. In those cases, we'll just blacklist those from testing
on v3.10.
Kevin
prev parent reply other threads:[~2015-07-10 18:51 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
2015-07-09 18:13 ` Kevin Hilman
2015-07-10 17:34 ` Greg Kroah-Hartman
2015-07-10 18:51 ` Kevin Hilman [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=7hfv4vals1.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--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).