From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6975FC4338F for ; Sat, 14 Aug 2021 22:31:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4EEA160F9F for ; Sat, 14 Aug 2021 22:31:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233780AbhHNWcS (ORCPT ); Sat, 14 Aug 2021 18:32:18 -0400 Received: from foss.arm.com ([217.140.110.172]:34692 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233223AbhHNWcR (ORCPT ); Sat, 14 Aug 2021 18:32:17 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id F404431B; Sat, 14 Aug 2021 15:31:47 -0700 (PDT) Received: from e113632-lin (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 4EC083F70D; Sat, 14 Aug 2021 15:31:47 -0700 (PDT) From: Valentin Schneider To: Guenter Roeck Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Marc Zyngier Subject: Re: [PATCH] irqchip/gic: Convert to handle_strict_flow_irq() In-Reply-To: <87sfzb7jeo.mognet@arm.com> References: <20210814194737.GA3951530@roeck-us.net> <87sfzb7jeo.mognet@arm.com> Date: Sat, 14 Aug 2021 23:31:45 +0100 Message-ID: <87pmuf7j5a.mognet@arm.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 14/08/21 23:26, Valentin Schneider wrote: > > Now, the above makes me feel like this is the start of a wild goose chase > for irqchips in a similar situation. The ones in arch/arm are easy enough to catch (I see gpc, omap-wakeupgen and some exynos suspend thing), less so for the ones in drivers/irqchip...