public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: maillist@chello.nl (Igmar Palsenberg),
	schwab@suse.de (Andreas Schwab),
	middelink@polyware.nl (Pauline Middelink),
	linux-kernel@vger.kernel.org
Subject: Re: linux-2.2.18-pre19 asm/delay.h problem?
Date: Thu, 23 Nov 2000 10:10:26 +0000	[thread overview]
Message-ID: <8307.974974226@redhat.com> (raw)
In-Reply-To: <E13yikV-0006ZQ-00@the-village.bc.nu>
In-Reply-To: <E13yikV-0006ZQ-00@the-village.bc.nu>


alan@lxorguk.ukuu.org.uk said:
> > |> Can't we change that to :
> > |> #error "Udelay..."
> > 
> > No.
> 
> ?? I think I'm missing something here.
> preprocessor stuff is done too early for this 

We were talking about

#if 0
/* Don't turn this on, fix your code instead */

void __bad_udelay(int c)
{
#error you broke it. read the damn comment
}
#endif

... so that when people search the tree for __bad_udelay they find this, 
and if they're silly enough to change the 0 to a 1 then it'll still break.

--
dwmw2


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-23 10:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-21 23:51 linux-2.2.18-pre19 asm/delay.h problem? jpranevich
2000-11-21 23:57 ` Alan Cox
2000-11-22  2:16   ` Peter Samuelson
2000-11-22  9:57   ` Rogier Wolff
2000-11-22 15:48     ` Pauline Middelink
2000-11-22 17:04       ` Igmar Palsenberg
2000-11-22 16:49         ` Andreas Schwab
2000-11-22 23:43           ` Igmar Palsenberg
2000-11-22 22:52             ` Alan Cox
2000-11-23 10:10               ` David Woodhouse [this message]
2000-11-24 17:15               ` Oliver Xymoron
2000-11-24 17:41                 ` Jeff Epler

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=8307.974974226@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maillist@chello.nl \
    --cc=middelink@polyware.nl \
    --cc=schwab@suse.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