All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [Patch] change if() BUG();
Date: Thu, 19 Jan 2006 02:53:36 +0000	[thread overview]
Message-ID: <20060119025336.GF19398@stusta.de> (raw)
In-Reply-To: <1137533116.20230.15.camel@alice>

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

On Wed, Jan 18, 2006 at 01:24:02AM +0300, Alexey Dobriyan wrote:
> On Tue, Jan 17, 2006 at 10:25:11PM +0100, Eric Sesterhenn / snakebyte wrote:
> > this patch changes the if() BUG(); construct in
> > drivers/net/ixgb/ixgb_osdep.h to a BUG_ON; so defining
> > BUG to a no-op is safe.
> 
> > --- linux-2.6.15-git11/drivers/net/ixgb/ixgb_osdep.h.orig
> > +++ linux-2.6.15-git11/drivers/net/ixgb/ixgb_osdep.h
> > @@ -60,7 +60,7 @@ typedef enum {
> >  } boolean_t;
> >
> >  #undef ASSERT
> > -#define ASSERT(x)	if(!(x)) BUG()
> > +#define ASSERT(x)	BUG_ON(!(x))
> 
> Naah. Just Drop It (TM).

AFAIR, this driver is both actively maintained by Intel and shared 
between operating systems (e.g. FreeBSD contains the same driver).

Therefore dropping this ASSERT is not possible.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


[-- Attachment #2: Type: text/plain, Size: 168 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

      parent reply	other threads:[~2006-01-19  2:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 21:25 [KJ] [Patch] change if() BUG(); Eric Sesterhenn / snakebyte
2006-01-17 22:24 ` Alexey Dobriyan
2006-01-19  2:53 ` Adrian Bunk [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=20060119025336.GF19398@stusta.de \
    --to=bunk@stusta.de \
    --cc=kernel-janitors@vger.kernel.org \
    /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.