All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ethan Nelson-Moore <enelsonmoore@gmail.com>
To: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Russell King <linux@armlinux.org.uk>,
	Ethan Nelson-Moore <enelsonmoore@gmail.com>
Subject: [PATCH] ARM: remove code to support non-sparse IRQs
Date: Sat,  9 May 2026 22:31:15 -0700	[thread overview]
Message-ID: <20260510053120.560874-1-enelsonmoore@gmail.com> (raw)

Now that footbridge and riscpc have been converted to sparse IRQs, this
code is unused. Remove it.

Signed-off-by: Ethan Nelson-Moore <enelsonmoore@gmail.com>
---
This commit depends on my previous submissions "ARM: riscpc: convert to
sparse IRQs" and "ARM: footbridge: convert to sparse IRQs".

 arch/arm/include/asm/irq.h | 5 -----
 arch/arm/kernel/irq.c      | 2 --
 2 files changed, 7 deletions(-)

diff --git a/arch/arm/include/asm/irq.h b/arch/arm/include/asm/irq.h
index 08589b88c3b9..449094a5044e 100644
--- a/arch/arm/include/asm/irq.h
+++ b/arch/arm/include/asm/irq.h
@@ -3,12 +3,7 @@
 #define __ASM_ARM_IRQ_H
 
 #define NR_IRQS_LEGACY	16
-
-#ifndef CONFIG_SPARSE_IRQ
-#include <mach/irqs.h>
-#else
 #define NR_IRQS NR_IRQS_LEGACY
-#endif
 
 #ifdef CONFIG_ARCH_FOOTBRIDGE
 #define irq_canonicalize(i)	(((i) == 2) ? 9 : i)
diff --git a/arch/arm/kernel/irq.c b/arch/arm/kernel/irq.c
index e1993e28a9ec..7458c529a489 100644
--- a/arch/arm/kernel/irq.c
+++ b/arch/arm/kernel/irq.c
@@ -148,9 +148,7 @@ void __init init_IRQ(void)
 	uniphier_cache_init();
 }
 
-#ifdef CONFIG_SPARSE_IRQ
 int __init arch_probe_nr_irqs(void)
 {
 	return irq_set_nr_irqs(machine_desc->nr_irqs ? : NR_IRQS);
 }
-#endif
-- 
2.43.0



                 reply	other threads:[~2026-05-10  5:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260510053120.560874-1-enelsonmoore@gmail.com \
    --to=enelsonmoore@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    /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.