[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140529182109.GA10142@kroah.com>
Date: Thu, 29 May 2014 11:21:09 -0700
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, satoru.takeuchi@...il.com,
shuah.kh@...sung.com, stable@...r.kernel.org
Subject: Re: [PATCH 3.14 000/140] 3.14.5-stable review
On Thu, May 29, 2014 at 08:06:10AM -0700, Guenter Roeck wrote:
> On 05/28/2014 09:32 PM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 3.14.5 release.
> >There are 140 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.
> >
> >Responses should be made by Sat May 31 04:30:12 UTC 2014.
> >Anything received after that time might be too late.
> >
>
> Build results:
> total: 143 pass: 133 skipped: 4 fail: 6
>
> Qemu tests all passed.
>
> Failing builds are
>
> alpha:defconfig - Fails with 'Inconsistent kallsyms data'. New failure; need to debug.
> unicore32:defconfig - still fails to build for all releases
> powerpc:allmodconfig - fail for binutils 2.3 and 2.4. known problem; patch pending
> powerpc:ppc64e_defconfig - fail if built with binutils 2.4; patch pending
> powerpc:chroma_defconfig - fail if built with binutils 2.4; patch pending
>
> Bisect points to commit 'vlan: Fix lockdep warning with stacked vlan devices' as culprit
> for the alpha:defconfig build failure. Reverting this patch fixes the problem.
> I looked at the patch, but I have no idea what may cause the failure.
Odd. Is this also broken in Linus's tree?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists