From: palmer@sifive.com (Palmer Dabbelt)
To: linux-arm-kernel@lists.infradead.org
Subject: Finish the GENERIC_IRQ_MULTI_HANDLER conversion
Date: Thu, 21 Jun 2018 11:17:51 -0700 [thread overview]
Message-ID: <20180621181756.12493-1-palmer@sifive.com> (raw)
A while ago I sent a patch set that adds a GENERIC_IRQ_MULTI_HANDLER,
which is an exact copy of the existing IRQ_MULTI_HANDLER support in the
arm port, which is being used unconditionally by arm64 and openrisc.
GENERIC_IRQ_MULTI_HANDLER is currently being used by the RISC-V port. I
managed to make a few mistakes in my original patch set and as a result
my conversion of the other architectures of GENERIC_IRQ_MULTI_HANDLER
was dropped.
This patch set finishes up my original patch set by converting arm,
arm64, and openrisc over to the new GENERIC_IRQ_MULTI_HANDLER support
and then removing MULTI_IRQ_HANDLER as it's obselete.
At the time I wrote this I gave it fairly extensive build testing, but
went I recently rebased it I just tested the full patch set on arm,
arm64, and openrisc defconfigs.
Various flavors of this patch set have bounced around a few times
before, but I'm calling this a whole new patch set as it builds on top
of what was merged.
next reply other threads:[~2018-06-21 18:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 18:17 Palmer Dabbelt [this message]
2018-06-22 17:01 ` Finish the GENERIC_IRQ_MULTI_HANDLER conversion Palmer Dabbelt
2018-06-22 17:01 ` [PATCH 1/5] irq: Port the ARM IRQ drivers to GENERIC_IRQ_MULTI_HANDLER Palmer Dabbelt
2018-06-22 17:01 ` [PATCH 2/5] arm: Convert " Palmer Dabbelt
2018-06-22 17:01 ` [PATCH 3/5] arm64: Use the new GENERIC_IRQ_MULTI_HANDLER Palmer Dabbelt
2018-06-22 17:01 ` [PATCH 4/5] openrisc: " Palmer Dabbelt
2018-06-22 17:01 ` [PATCH 5/5] irq: Remove MULTI_IRQ_HANDLER as it's now obselete Palmer Dabbelt
2018-06-24 13:15 ` Finish the GENERIC_IRQ_MULTI_HANDLER conversion Thomas Gleixner
2018-08-02 18:30 ` Palmer Dabbelt
2018-08-03 10:09 ` Thomas Gleixner
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=20180621181756.12493-1-palmer@sifive.com \
--to=palmer@sifive.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox