LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Valentin Schneider <valentin.schneider@arm.com>
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 16:41:03 -0700 [thread overview]
Message-ID: <20210814234103.GA828447@roeck-us.net> (raw)
In-Reply-To: <87pmuf7j5a.mognet@arm.com>
On Sat, Aug 14, 2021 at 11:31:45PM +0100, Valentin Schneider wrote:
> 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...
Try:
make coccicheck COCCI=irq_chip.cocci MODE=report M=.
with the script below. I am sure the script could be augmented if
there is some secondary condition that makes irq_ack mandatory.
Guenter
---
irq_chip.cocci:
virtual report
@c@
identifier chip;
position p;
@@
struct irq_chip chip@p = {
...
};
@i@
identifier c.chip;
identifier f;
@@
struct irq_chip chip = {
.irq_ack = f,
};
@script:python depends on c && !i && report@
p << c.p;
@@
print "Found %s:%s" % (p[0].file, p[0].line)
next prev parent reply other threads:[~2021-08-14 23:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 19:47 Guenter Roeck
2021-08-14 22:26 ` Valentin Schneider
2021-08-14 22:31 ` Valentin Schneider
2021-08-14 23:41 ` Guenter Roeck [this message]
2021-08-14 23:15 ` Guenter Roeck
2021-08-14 23:36 ` Guenter Roeck
2021-08-15 7:01 ` Marc Zyngier
2021-08-15 6:54 ` Marc Zyngier
2021-08-17 0:30 ` Valentin Schneider
2021-08-18 16:58 ` Marc Zyngier
2021-08-22 22:16 ` Valentin Schneider
2021-08-23 9:33 ` Marc Zyngier
2021-08-23 10:38 ` Valentin Schneider
2021-08-23 12:17 ` Marc Zyngier
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=20210814234103.GA828447@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=valentin.schneider@arm.com \
--subject='Re: [PATCH] irqchip/gic: Convert to handle_strict_flow_irq()' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).