From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kevin Hilman <khilman@baylibre.com>
Cc: "kernelci.org bot" <bot@kernelci.org>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net,
shuah.kh@samsung.com, patches@kernelci.org,
ben.hutchings@codethink.co.uk, stable@vger.kernel.org,
alexandre.belloni@free-electrons.com,
quentin.schulz@free-electrons.com, sjoerd.simons@collabora.co.uk
Subject: Re: [PATCH 4.4 00/13] 4.4.37-stable review
Date: Thu, 8 Dec 2016 17:25:46 +0100 [thread overview]
Message-ID: <20161208162546.GC13456@kroah.com> (raw)
In-Reply-To: <m2inqvekqu.fsf@baylibre.com>
On Wed, Dec 07, 2016 at 09:01:45AM -0800, Kevin Hilman wrote:
> + some lab owners at Free Electrons, Collabora
>
> kernelci.org bot <bot@kernelci.org> writes:
>
> > stable-rc boot: 156 boots: 2 failed, 153 passed with 1 conflict (v4.4.36-14-g322b9514f86e)
> >
> > Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/kernel/v4.4.36-14-g322b9514f86e/
> > Full Build Summary: https://kernelci.org/build/stable-rc/kernel/v4.4.36-14-g322b9514f86e/
> >
> > Tree: stable-rc
> > Branch: local/linux-4.4.y
> > Git Describe: v4.4.36-14-g322b9514f86e
> > Git Commit: 322b9514f86ef1be23ca2b50e0541d4d5e2d6bf3
> > Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > Tested: 37 unique boards, 10 SoC families, 21 builds out of 202
> >
> > Boot Regressions Detected:
> >
> > arm:
> >
> > multi_v7_defconfig+CONFIG_LKDTM=y:
> > am335x-boneblack:
> > lab-collabora: new failure (last pass: v4.4.35-23-g6a11a03c8a3c)
>
> This one looks lab specific, as it passed in 2 other labs.
>
> > multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
> > sama5d36ek:
> > lab-free-electrons: failing since 38 days (last pass: v4.4.13-82-g832ada1e8e08 - first fail: v4.4.28-52-g801f6b993dc2)
>
> This one has been failing for awhile. Cc'd lab owners at Free
> Electrons.
>
> > multi_v7_defconfig+CONFIG_SMP=n:
> > imx6q-sabrelite:
> > lab-collabora: failing since 14 days (last pass: v4.4.32-28-gd60fb7232229 - first fail: v4.4.34)
>
> Also not a new one. Cc'd lab owners at collabora.
>
> Otherwise, intrepretation: no blocking issues.
Great, thanks for letting me know.
greg k-h
next prev parent reply other threads:[~2016-12-08 16:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161207070805epcas3p1487b13063215635759cae58441ad906a@epcas3p1.samsung.com>
2016-12-07 7:07 ` [PATCH 4.4 00/13] 4.4.37-stable review Greg Kroah-Hartman
2016-12-07 7:07 ` [PATCH 4.4 01/13] ARC: Dont use "+l" inline asm constraint Greg Kroah-Hartman
2016-12-07 7:07 ` [PATCH 4.4 02/13] zram: fix unbalanced idr management at hot removal Greg Kroah-Hartman
2016-12-07 7:07 ` [PATCH 4.4 03/13] kasan: update kasan_global for gcc 7 Greg Kroah-Hartman
2016-12-07 7:07 ` [PATCH 4.4 04/13] x86/traps: Ignore high word of regs->cs in early_fixup_exception() Greg Kroah-Hartman
2016-12-07 7:07 ` [PATCH 4.4 05/13] ALSA: pcm : Call kill_fasync() in stream lock Greg Kroah-Hartman
2016-12-07 7:07 ` [PATCH 4.4 06/13] rcu: Fix soft lockup for rcu_nocb_kthread Greg Kroah-Hartman
2016-12-07 7:07 ` [PATCH 4.4 07/13] PCI: Export pcie_find_root_port Greg Kroah-Hartman
2016-12-07 7:07 ` [PATCH 4.4 09/13] mwifiex: printk() overflow with 32-byte SSIDs Greg Kroah-Hartman
2016-12-07 7:07 ` [PATCH 4.4 10/13] pwm: Fix device reference leak Greg Kroah-Hartman
2016-12-07 7:07 ` [PATCH 4.4 11/13] arm64: cpufeature: Schedule enable() calls instead of calling them via IPI Greg Kroah-Hartman
2016-12-07 7:07 ` [PATCH 4.4 12/13] arm64: mm: Set PSTATE.PAN from the cpu_enable_pan() call Greg Kroah-Hartman
2016-12-07 7:07 ` [PATCH 4.4 13/13] arm64: suspend: Reconfigure PSTATE after resume from idle Greg Kroah-Hartman
2016-12-07 16:07 ` [PATCH 4.4 00/13] 4.4.37-stable review Guenter Roeck
2016-12-07 18:17 ` Shuah Khan
[not found] ` <5847f96a.45f6c20a.fab5.7b38@mx.google.com>
[not found] ` <m2inqvekqu.fsf@baylibre.com>
2016-12-08 16:25 ` Greg Kroah-Hartman [this message]
2016-12-07 7:35 Philip Müller
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=20161208162546.GC13456@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=ben.hutchings@codethink.co.uk \
--cc=bot@kernelci.org \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=patches@kernelci.org \
--cc=quentin.schulz@free-electrons.com \
--cc=shuah.kh@samsung.com \
--cc=sjoerd.simons@collabora.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.