From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753760AbbHaQrm (ORCPT ); Mon, 31 Aug 2015 12:47:42 -0400 Received: from bh-25.webhostbox.net ([208.91.199.152]:42773 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753322AbbHaQrl (ORCPT ); Mon, 31 Aug 2015 12:47:41 -0400 Message-ID: <55E48529.5070907@roeck-us.net> Date: Mon, 31 Aug 2015 09:47:37 -0700 From: Guenter Roeck User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0 MIME-Version: 1.0 To: Stephen Rothwell , Thomas Gleixner CC: Linus Torvalds , LKML , Andrew Morton , Ingo Molnar , "H. Peter Anvin" , Marc Zyngier Subject: Re: [GIT pull] irq updates for 4.3 References: <20150901021246.0ace2c6d@canb.auug.org.au> In-Reply-To: <20150901021246.0ace2c6d@canb.auug.org.au> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated_sender: linux@roeck-us.net X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - roeck-us.net X-Get-Message-Sender-Via: bh-25.webhostbox.net: authenticated_id: linux@roeck-us.net X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/31/2015 09:12 AM, Stephen Rothwell wrote: > Hi Thomas, > > On Mon, 31 Aug 2015 12:04:37 +0200 (CEST) Thomas Gleixner wrote: >> >> Marc Zyngier (23): >> irqchip/GIC: Convert to EOImode == 1 > > This appears to lead to qemu arm boot tests silently failing (according > to Guenter). This commit only appeared in next-20150831. > I think we really need more time between patches showing up in -next and being pushed upstream. We have several new failures in -next which were introduced after next-20150828, with this being the most serious one. Of course, that additional time doesn't help if failures in -next are known for weeks and still end up in mainline. Not really sure how to solve that problem. Guenter