public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Kevin Hilman <khilman@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Cc: 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: Wed, 10 Jun 2015 22:39:52 -0400	[thread overview]
Message-ID: <5578F4F8.7090805@oracle.com> (raw)
In-Reply-To: <CAMAWPa9yMyehRhoTkvyxKo5rOPk+qhbH1MWuUUr7n-6sFY2COg@mail.gmail.com>

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.


Thanks,
Sasha


  parent reply	other threads:[~2015-06-11  2:40 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 [this message]
2015-06-11 17:52     ` Kevin Hilman
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=5578F4F8.7090805@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=khilman@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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