From: tip-bot for Geert Uytterhoeven <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: hpa@zytor.com, geert+renesas@glider.be, marc.zyngier@arm.com,
tglx@linutronix.de, linux-kernel@vger.kernel.org,
mingo@kernel.org
Subject: [tip:irq/core] genirq/irqdomain: Remove WARN_ON() on out-of-memory condition
Date: Tue, 28 May 2019 13:23:57 -0700 [thread overview]
Message-ID: <tip-43b98d876f89dce732f50b71607b6d2bbb8d8e6a@git.kernel.org> (raw)
In-Reply-To: <20190527115742.2693-1-geert+renesas@glider.be>
Commit-ID: 43b98d876f89dce732f50b71607b6d2bbb8d8e6a
Gitweb: https://git.kernel.org/tip/43b98d876f89dce732f50b71607b6d2bbb8d8e6a
Author: Geert Uytterhoeven <geert+renesas@glider.be>
AuthorDate: Mon, 27 May 2019 13:57:42 +0200
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Tue, 28 May 2019 13:10:55 -0700
genirq/irqdomain: Remove WARN_ON() on out-of-memory condition
There is no need to print a backtrace when memory allocation fails, as
the memory allocation core already takes care of that.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Marc Zyngier <marc.zyngier@arm.com>
Link: https://lkml.kernel.org/r/20190527115742.2693-1-geert+renesas@glider.be
---
kernel/irq/irqdomain.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
index a453e229f99c..e7d17cc3a3d7 100644
--- a/kernel/irq/irqdomain.c
+++ b/kernel/irq/irqdomain.c
@@ -139,7 +139,7 @@ struct irq_domain *__irq_domain_add(struct fwnode_handle *fwnode, int size,
domain = kzalloc_node(sizeof(*domain) + (sizeof(unsigned int) * size),
GFP_KERNEL, of_node_to_nid(of_node));
- if (WARN_ON(!domain))
+ if (!domain)
return NULL;
if (fwnode && is_fwnode_irqchip(fwnode)) {
next prev parent reply other threads:[~2019-05-28 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 11:57 [PATCH] " Geert Uytterhoeven
2019-05-28 20:23 ` tip-bot for Geert Uytterhoeven [this message]
2019-05-28 22:54 ` [tip:irq/core] " Joe Perches
2019-05-28 23:00 ` Gustavo A. R. Silva
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-43b98d876f89dce732f50b71607b6d2bbb8d8e6a@git.kernel.org \
--to=tipbot@zytor.com \
--cc=geert+renesas@glider.be \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mingo@kernel.org \
--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
Powered by JetHome