From: tip-bot for RAGHU Halharvi <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: raghuhack78@gmail.com, mingo@kernel.org,
linux-kernel@vger.kernel.org, hpa@zytor.com, tglx@linutronix.de
Subject: [tip:irq/core] genirq: Remove redundant NULL pointer check in __free_irq()
Date: Tue, 17 Jul 2018 04:39:58 -0700 [thread overview]
Message-ID: <tip-d91cfeb0aa79445fcfa9f523a5b57c5e9f4113ec@git.kernel.org> (raw)
In-Reply-To: <20180717102009.7708-1-raghuhack78@gmail.com>
Commit-ID: d91cfeb0aa79445fcfa9f523a5b57c5e9f4113ec
Gitweb: https://git.kernel.org/tip/d91cfeb0aa79445fcfa9f523a5b57c5e9f4113ec
Author: RAGHU Halharvi <raghuhack78@gmail.com>
AuthorDate: Tue, 17 Jul 2018 15:50:09 +0530
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Tue, 17 Jul 2018 13:35:44 +0200
genirq: Remove redundant NULL pointer check in __free_irq()
The NULL pointer check in __free_irq() triggers a 'dereference before NULL
pointer check' warning in static code analysis. It turns out that the check
is redundant because all callers have a NULL pointer check already.
Remove it.
Signed-off-by: RAGHU Halharvi <raghuhack78@gmail.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lkml.kernel.org/r/20180717102009.7708-1-raghuhack78@gmail.com
---
kernel/irq/manage.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index 1f8be33572a7..a66c58f91bff 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -1570,9 +1570,6 @@ static struct irqaction *__free_irq(struct irq_desc *desc, void *dev_id)
WARN(in_interrupt(), "Trying to free IRQ %d from IRQ context!\n", irq);
- if (!desc)
- return NULL;
-
mutex_lock(&desc->request_mutex);
chip_bus_lock(desc);
raw_spin_lock_irqsave(&desc->lock, flags);
prev parent reply other threads:[~2018-07-17 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.21.1807171100590.3238@nanos.tec.linutronix.de>
2018-07-17 10:20 ` [PATCH] genirq:free_irq:remove redundant null ptr check RAGHU Halharvi
2018-07-17 11:39 ` tip-bot for RAGHU Halharvi [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=tip-d91cfeb0aa79445fcfa9f523a5b57c5e9f4113ec@git.kernel.org \
--to=tipbot@zytor.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=raghuhack78@gmail.com \
--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 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).