From: "David D. Hagood" <wowbagger@sktc.net>
To: Christophe Saout <christophe@saout.de>
Cc: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
linux-kernel@vger.kernel.org
Subject: Re: [FUN] Re: [PATCH] Move BUG/BUG_ON/WARN_ON to asm headers
Date: Sat, 07 Jun 2003 19:26:28 -0500 [thread overview]
Message-ID: <3EE282B4.2010207@sktc.net> (raw)
In-Reply-To: <1055028601.7146.0.camel@chtephan.cs.pocnet.net>
Christophe Saout wrote:
> Hi Ingo!
>
>> On Sat, Jun 07, 2003 at 10:40:08PM +1000, Paul Mackerras wrote:
>> > +struct bug_entry *module_find_bug(unsigned long bugaddr)
>>
>> A wet dream of many driver writers has come true: A function,
>> which finds the bug in their module ;-)
>
> *The* bug? That sounds very optimistic. ;-)
>
Well, y'just gotta iterate...
struct bug_entry *x = module_find_bug(my_module);
while (x)
{
module_fix_bug(my_module,x);
x = module_find_bug(my_module)
}
So, who will write module_fix_bug?
next prev parent reply other threads:[~2003-06-08 0:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-07 12:40 [PATCH] Move BUG/BUG_ON/WARN_ON to asm headers Paul Mackerras
2003-06-07 12:56 ` [FUN] " Ingo Oeser
2003-06-07 23:30 ` Christophe Saout
2003-06-08 0:26 ` David D. Hagood [this message]
2003-06-07 15:43 ` Bartlomiej Zolnierkiewicz
2003-06-08 18:12 ` Linus Torvalds
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=3EE282B4.2010207@sktc.net \
--to=wowbagger@sktc.net \
--cc=christophe@saout.de \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@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.