[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <30490ca3-b741-016c-4912-e2057dd50994@suse.cz>
Date: Fri, 27 Jan 2017 20:04:20 +0100
From: Jiri Slaby <jslaby@...e.cz>
To: Guenter Roeck <linux@...ck-us.net>
Cc: stable@...r.kernel.org, shuahkh@....samsung.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3.12 000/235] 3.12.70-stable review
On 01/27/2017, 06:23 PM, Guenter Roeck wrote:
> Hi Jiri,
>
> On Fri, Jan 27, 2017 at 11:55:00AM +0100, Jiri Slaby wrote:
>> This is the start of the stable review cycle for the 3.12.70 release.
>> There are 235 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 Tue Jan 31 11:52:54 CET 2017.
>> Anything received after that time might be too late.
>>
>
> Looks like something slipped in last minute.
>
> Build results:
> total: 128 pass: 115 fail: 13
> Failed builds:
> alpha:allmodconfig
> arm:allmodconfig
> arm64:allmodconfig
> i386:allyesconfig
> i386:allmodconfig
> m68k:allmodconfig
> mips:allmodconfig
> powerpc:allmodconfig
> s390:allmodconfig
> sparc64:allmodconfig
> x86_64:allyesconfig
> x86_64:allmodconfig
> xtensa:allmodconfig
>
> security/apparmor/lsm.c: In function 'apparmor_setprocattr':
> security/apparmor/lsm.c:565:29: error: 'largs' undeclared
Yes, I dropped one apparmor patch and it broke a later patch. I dropped
it 2 hours ago too, so what is building now on the machines should be
fine, hopefully.
thanks,
--
js
suse labs
Powered by blists - more mailing lists