Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp1496284ybh; Sun, 15 Mar 2020 04:21:58 -0700 (PDT) X-Google-Smtp-Source: ADFU+vtoHXTbuDzn33wpXLLllUmd4H2IAGbr9Dl58GjAh7X51cyujelF2mRWv/WtbrryDCFlLP0X X-Received: by 2002:a9d:638a:: with SMTP id w10mr12625771otk.103.1584271318086; Sun, 15 Mar 2020 04:21:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584271318; cv=none; d=google.com; s=arc-20160816; b=iLMW74KaQv/8z4mcMH1uQNMyoFcJEJJFz3zXXHn186CQoShM03MI/1gWgzl4Yj3CcS k9v3tR30VVgBk4ISbAwuCejQQuGTRIlVsh3qyIVLTpVBsSdwq0w7r5tpltnZWWIWR81m lxSdfAsF19LQfyODCbDmRxysS7Zdk6V3c+yKq5vEGC0WJYjbaHIHSlmoTS6j7n7l/KXd iEz5seGDwqheKjjJc18AqwT73yVJdtGFqQyuwGV9M1j/ynS7pbOH90S2K8PY9HtEuGhH Iepz+NbIuOL+/QK/h4oXTlUvBX8VqM4PLYXBkafYgu9yG5rFvAWHalt1Ft2wQlDVRHBA Qlog== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=xTI0fIvxlUl50p6RBTTaOzqXw5Fl2RrNA/ooR16y8xg=; b=y92Pp/K8vQShs55CXqBjr9A6zXdzvkv00Drz35yqjbKgR1CGulxuI84mQbUCl5w+Fd KYjQdQyb+qs3AtbZJzVObHJtYxtM6dKADNij5CbVvx73+OxfHLassymVip1yLId8Ec/1 tMmi6uUWVsRAqblkTnZJmevOOS8hrJzQ9Sda5IGMefiGmRblSbgljt2OFPKB8OXftD9X sAjJWxA59JhXFm1VtPiLoDvvEURjnJAG6mrDHcWBvk24lCdrQjRXYKAdyy8UtrXq7Ucj 47r+n1Prv6LiFLDAUe8s/zrEh6Gqvcc/xScSwZUkkBgmbDvMBu7hDj1KW41FGKb3YL+x J8UQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j185si5976472oif.36.2020.03.15.04.21.45; Sun, 15 Mar 2020 04:21:58 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728336AbgCOLVX (ORCPT + 99 others); Sun, 15 Mar 2020 07:21:23 -0400 Received: from bmailout2.hostsharing.net ([83.223.78.240]:59921 "EHLO bmailout2.hostsharing.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728234AbgCOLVX (ORCPT ); Sun, 15 Mar 2020 07:21:23 -0400 Received: from h08.hostsharing.net (h08.hostsharing.net [83.223.95.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.hostsharing.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified)) by bmailout2.hostsharing.net (Postfix) with ESMTPS id 85FC22800B1B3; Sun, 15 Mar 2020 12:21:21 +0100 (CET) Received: by h08.hostsharing.net (Postfix, from userid 100393) id 522C71CDF33; Sun, 15 Mar 2020 12:21:21 +0100 (CET) Date: Sun, 15 Mar 2020 12:21:21 +0100 From: Lukas Wunner To: Marc Zyngier Cc: Thomas Gleixner , Catalin Marinas , Mark Salter , Robert Richter , Tim Harvey , Jason Cooper , linux-kernel@vger.kernel.org Subject: Re: [GIT PULL] irqchip fixes for 5.6, take #2 Message-ID: <20200315112121.n5mucfsibs2eeudg@wunner.de> References: <20200314103000.2413-1-maz@kernel.org> <20200315084846.h222n5pf4jvpojec@wunner.de> <76dcc2d8532f8e3a87bf03469b9c2c19@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <76dcc2d8532f8e3a87bf03469b9c2c19@kernel.org> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Mar 15, 2020 at 10:13:38AM +0000, Marc Zyngier wrote: > On 2020-03-15 08:48, Lukas Wunner wrote: > > Hm, I was hoping to see the BCM2835 irqchip fix in this pull: > > > > https://lore.kernel.org/lkml/f97868ba4e9b86ddad71f44ec9d8b3b7d8daa1ea.1582618537.git.lukas@wunner.de/ > > Whilst I don't dispute that this patch addresses a serious issue, > it is in no way an urgent fix -- the issue is already 7.5 year old, > so a couple of week delay isn't going to change the world. Also, > the system does work without this fix, so I'm quite confident > leaving it for 5.7. > > But thanks for this email anyway, as it reminded me that although > I had picked that patch for 5.7, I didn't apply it just yet. This > is now fixed, and the patch should be picked up by -next shortly. Sure, fair enough, thanks. Bonne fin de week-end, Lukas