From: Thomas Gleixner <tglx@linutronix.de>
To: Maninder Singh <maninder1.s@samsung.com>
Cc: Jason Cooper <jason@lakedaemon.net>,
LKML <linux-kernel@vger.kernel.org>,
pankaj.m@samsung.com, Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [PATCH 1/1] irq-gic: use BUG_ON instead of if()/BUG
Date: Fri, 19 Jun 2015 11:32:03 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1506191126380.4107@nanos> (raw)
In-Reply-To: <1434703938-19180-1-git-send-email-maninder1.s@samsung.com>
On Fri, 19 Jun 2015, Maninder Singh wrote:
> Use BUG_ON(condition) instead of if(condition)/BUG()
> As given in scripts/coccinelle/misc/bugon.cocci
>
> Signed-off-by: Maninder Singh <maninder1.s@samsung.com>
> Reviewed-by: Vaneet Narang <v.narang@samsung.com>
> ---
> drivers/irqchip/irq-gic.c | 18 ++++++------------
> 1 file changed, 6 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
> index 8d7e1c8..b222c7b 100644
> --- a/drivers/irqchip/irq-gic.c
> +++ b/drivers/irqchip/irq-gic.c
> @@ -329,8 +329,7 @@ static struct irq_chip gic_chip = {
>
> void __init gic_cascade_irq(unsigned int gic_nr, unsigned int irq)
> {
> - if (gic_nr >= MAX_GIC_NR)
> - BUG();
> + BUG_ON(gic_nr >= MAX_GIC_NR);
> if (irq_set_handler_data(irq, &gic_data[gic_nr]) != 0)
> BUG();
So this patch was clearly done just by running a script and not sanity
checked afterwards. Otherwise the next if() BUG(); construct would
have been fixed as well.
Further, while we are at that. It would be even more useful to analyze
whether the BUG_ON() is needed in the first place or at least could be
made conditional on some debug option.
But that's not done by the script either, right?
Thanks,
tglx
next prev parent reply other threads:[~2015-06-19 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 8:52 Maninder Singh
2015-06-19 9:32 ` Thomas Gleixner [this message]
2015-06-19 9:51 Maninder Singh
2015-06-19 10:07 ` Thomas Gleixner
2015-06-22 13:05 Maninder Singh
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=alpine.DEB.2.11.1506191126380.4107@nanos \
--to=tglx@linutronix.de \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maninder1.s@samsung.com \
--cc=marc.zyngier@arm.com \
--cc=pankaj.m@samsung.com \
/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
all inboxes | Powered by JetHome®