From: "irqchip-bot for Yanteng Si" <tip-bot2@linutronix.de>
To: linux-kernel@vger.kernel.org
Cc: Yanteng Si <siyanteng@loongson.cn>, Marc Zyngier <maz@kernel.org>,
tglx@linutronix.de
Subject: [irqchip: irq/irqchip-next] MIPS: irq: Avoid an unused-variable error
Date: Thu, 28 Oct 2021 13:23:24 -0000 [thread overview]
Message-ID: <163542740410.626.5186631730404597986.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20211028095652.3503790-1-siyanteng@loongson.cn>
The following commit has been merged into the irq/irqchip-next branch of irqchip:
Commit-ID: 34fca8947b2743e6a3a9a8a3a44962e625993533
Gitweb: https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms/34fca8947b2743e6a3a9a8a3a44962e625993533
Author: Yanteng Si <siyanteng01@gmail.com>
AuthorDate: Thu, 28 Oct 2021 17:56:52 +08:00
Committer: Marc Zyngier <maz@kernel.org>
CommitterDate: Thu, 28 Oct 2021 13:28:52 +01:00
MIPS: irq: Avoid an unused-variable error
When CONFIG_IRQ_DOMAIN is set, there is a warning:
arch/mips/kernel/irq.c:114:19: error: unused variable 'desc' [-Werror=unused-variable]
114 | struct irq_desc *desc;
| ^~~~
This variable is unused, let's remove it.
Signed-off-by: Yanteng Si <siyanteng@loongson.cn>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20211028095652.3503790-1-siyanteng@loongson.cn
---
arch/mips/kernel/irq.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/mips/kernel/irq.c b/arch/mips/kernel/irq.c
index 1fee96e..5e11582 100644
--- a/arch/mips/kernel/irq.c
+++ b/arch/mips/kernel/irq.c
@@ -111,8 +111,6 @@ void __irq_entry do_IRQ(unsigned int irq)
#ifdef CONFIG_IRQ_DOMAIN
void __irq_entry do_domain_IRQ(struct irq_domain *domain, unsigned int hwirq)
{
- struct irq_desc *desc;
-
irq_enter();
check_stack_overflow();
generic_handle_domain_irq(domain, hwirq);
prev parent reply other threads:[~2021-10-28 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 9:56 [PATCH] MIPS: irq: avoid an unused-variable error Yanteng Si
2021-10-28 13:23 ` irqchip-bot for Yanteng Si [this message]
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=163542740410.626.5186631730404597986.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=siyanteng@loongson.cn \
--cc=tglx@linutronix.de \
/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.