Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755054AbbFKRwK (ORCPT ); Thu, 11 Jun 2015 13:52:10 -0400 Received: from mail-pd0-f177.google.com ([209.85.192.177]:34229 "EHLO mail-pd0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754163AbbFKRwH (ORCPT ); Thu, 11 Jun 2015 13:52:07 -0400 From: Kevin Hilman To: Sasha Levin Cc: lkml , stable@vger.kernel.org, stable-commits@vger.kernel.org, Tyler Baker , Guenter Roeck Subject: Re: [PATCH 3.18 000/178] 3.18.15-review References: <1433770969-2003-1-git-send-email-sasha.levin@oracle.com> <5578F4F8.7090805@oracle.com> Date: Thu, 11 Jun 2015 10:52:00 -0700 In-Reply-To: <5578F4F8.7090805@oracle.com> (Sasha Levin's message of "Wed, 10 Jun 2015 22:39:52 -0400") Message-ID: <7hr3pif7zz.fsf@deeprootsystems.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2357 Lines: 64 Sasha Levin writes: > On 06/09/2015 01:17 PM, Kevin Hilman wrote: >> Hi Sasha, >> >> On Mon, Jun 8, 2015 at 6:39 AM, Sasha Levin wrote: >>> This is the start of the stable review cycle for the 3.18.15 release. >>> There are 178 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. >> >> We've started build/boot testing your 3.18 stable queue with the >> automated build/boot tools at the kernelci.org project. We'll soon be >> sending automated reports to this list for your stable queue (and >> other stable trees.) Until we have the email reports automated, below >> is the report for this review series which has a whole pile of build >> failures across x86, arm and arm64. >> >> Kevin > > Thanks for the report(s)! > > I've fixed the issues and re-pushed. > Build looks good now. I only have one remaining build failure[1] for ARM multi_v7_defconfig with CONFIG_THUMB2_KERNEL=y enabled[1]. I had already posted a fix for that patch to stable, but it's missing in your queue so I replied to that patch to help you find it. It also looks good for boot testing at kernelci.org[2]. The boot failures here aren't specific to your queue, but are NFSroot issues for these boards with v3.18 in general. Thanks, Kevin [1] http://kernelci.org/build/stable-sasha/kernel/v3.18.14-167-g25798d3d2163/?fail [2] stable-sasha boot: 206 boots: 4 failed, 202 passed (v3.18.14-167-g25798d3d2163) Full Boot Summary: http://kernelci.org/boot/all/job/stable-sasha/kernel/v3.18.14-167-g25798d3d2163/ Full Build Summary: http://kernelci.org/build/stable-sasha/kernel/v3.18.14-167-g25798d3d2163/ Tree: stable-sasha Branch: local/linux-3.18.y-queue Git Describe: v3.18.14-167-g25798d3d2163 Git Commit: 25798d3d216334361a51ac37429a83c1faa5e97d Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git Tested: 67 unique boards, 19 SoC families, 26 builds out of 143 Boot Failures Detected: http://kernelci.org/boot/?v3.18.14-167-g25798d3d2163&fail -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/