From: Valentin Schneider <valentin.schneider@arm.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH] irqchip/gic: Convert to handle_strict_flow_irq()
Date: Sat, 14 Aug 2021 23:31:45 +0100 [thread overview]
Message-ID: <87pmuf7j5a.mognet@arm.com> (raw)
In-Reply-To: <87sfzb7jeo.mognet@arm.com>
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...
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Valentin Schneider <valentin.schneider@arm.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH] irqchip/gic: Convert to handle_strict_flow_irq()
Date: Sat, 14 Aug 2021 23:31:45 +0100 [thread overview]
Message-ID: <87pmuf7j5a.mognet@arm.com> (raw)
In-Reply-To: <87sfzb7jeo.mognet@arm.com>
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...
next prev parent reply other threads:[~2021-08-14 22:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 19:47 [PATCH] irqchip/gic: Convert to handle_strict_flow_irq() Guenter Roeck
2021-08-14 22:26 ` Valentin Schneider
2021-08-14 22:26 ` Valentin Schneider
2021-08-14 22:31 ` Valentin Schneider [this message]
2021-08-14 22:31 ` Valentin Schneider
2021-08-14 23:41 ` Guenter Roeck
2021-08-14 23:41 ` Guenter Roeck
2021-08-14 23:15 ` Guenter Roeck
2021-08-14 23:15 ` Guenter Roeck
2021-08-14 23:36 ` Guenter Roeck
2021-08-14 23:36 ` Guenter Roeck
2021-08-15 7:01 ` Marc Zyngier
2021-08-15 7:01 ` Marc Zyngier
2021-08-15 6:54 ` Marc Zyngier
2021-08-15 6:54 ` Marc Zyngier
2021-08-17 0:30 ` Valentin Schneider
2021-08-17 0:30 ` Valentin Schneider
2021-08-18 16:58 ` Marc Zyngier
2021-08-18 16:58 ` Marc Zyngier
2021-08-22 22:16 ` Valentin Schneider
2021-08-22 22:16 ` Valentin Schneider
2021-08-23 9:33 ` Marc Zyngier
2021-08-23 9:33 ` Marc Zyngier
2021-08-23 10:38 ` Valentin Schneider
2021-08-23 10:38 ` Valentin Schneider
2021-08-23 12:17 ` Marc Zyngier
2021-08-23 12:17 ` Marc Zyngier
2021-08-30 16:54 ` Valentin Schneider
2021-08-30 16:54 ` Valentin Schneider
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmuf7j5a.mognet@arm.com \
--to=valentin.schneider@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=maz@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.