[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Ycc1squoiTh0iyM/@lunn.ch>
Date: Sat, 25 Dec 2021 16:16:02 +0100
From: Andrew Lunn <andrew@...n.ch>
To: "Lad, Prabhakar" <prabhakar.csengg@...il.com>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/8] net: pxa168_eth: Use platform_get_irq() to get the
interrupt
> >> + goto err_netdev;
> >> + BUG_ON(dev->irq < 0);
> >
> >
> > ??? What is this and how it supposed to work?
> >
> .. should have been BUG_ON(dev->irq < 0);
Is this fatal to the machine as a whole, now way to recover, all that
can be done is to limit the damage while it explodes?
If not, please use WARN_ON(), not BUG_ON(). There is an email from
Linus about this, not using BUG_ON() in general.
Andrew
Powered by blists - more mailing lists