public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@kernel.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	stable@vger.kernel.org, stable-commits@vger.kernel.org,
	Tyler Baker <tyler.baker@linaro.org>,
	Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH 3.18 000/178] 3.18.15-review
Date: Thu, 11 Jun 2015 10:52:00 -0700	[thread overview]
Message-ID: <7hr3pif7zz.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5578F4F8.7090805@oracle.com> (Sasha Levin's message of "Wed, 10 Jun 2015 22:39:52 -0400")

Sasha Levin <sasha.levin@oracle.com> writes:

> On 06/09/2015 01:17 PM, Kevin Hilman wrote:
>> Hi Sasha,
>> 
>> On Mon, Jun 8, 2015 at 6:39 AM, Sasha Levin <sasha.levin@oracle.com> 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


  reply	other threads:[~2015-06-11 17:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1433770969-2003-1-git-send-email-sasha.levin@oracle.com>
2015-06-09 17:17 ` [PATCH 3.18 000/178] 3.18.15-review Kevin Hilman
2015-06-10  5:24   ` Guenter Roeck
2015-06-11  2:39   ` Sasha Levin
2015-06-11 17:52     ` Kevin Hilman [this message]
2015-06-11 17:58       ` 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=7hr3pif7zz.fsf@deeprootsystems.com \
    --to=khilman@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=sasha.levin@oracle.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tyler.baker@linaro.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