From: Keith Owens <kaos@ocs.com.au>
To: Martin Wilck <Martin.Wilck@fujitsu-siemens.com>
Cc: Jamie Lokier <lk@tantalophile.demon.co.uk>,
Andreas Dilger <adilger@clusterfs.com>,
Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Cleanup port 0x80 use (was: Re: IO delay ...)
Date: Mon, 18 Mar 2002 20:39:18 +1100 [thread overview]
Message-ID: <4463.1016444358@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 18 Mar 2002 10:18:06 BST." <Pine.LNX.4.33.0203180938060.9609-100000@biker.pdb.fsc.net>
On Mon, 18 Mar 2002 10:18:06 +0100 (CET),
Martin Wilck <Martin.Wilck@fujitsu-siemens.com> wrote:
>On Sun, 17 Mar 2002, Jamie Lokier wrote:
>
>> As long as __SLOW_DOWN_IO_PORT is a simple constant, you can just use
>> this instead:
>>
>> #define __SLOW_DOWN_IO_ASM "\noutb %%al,$" #__SLOW_DOWN_IO_PORT
>
>What cpp are you guys using? Mine does stringification (#s) only with
>arguments of function-like macros. However
Recent 2.4 and 2.5 kernels have include/linux/stringify.h. This should
work.
#define __SLOW_DOWN_IO_ASM "\noutb %%al,$" __stringify(__SLOW_DOWN_IO_PORT)
next prev parent reply other threads:[~2002-03-18 9:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C90E983.5AC769B8@ngforever.de.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.33.0203151243430.1477-100000@biker.pdb.fsc.net.suse.lists.linux.kernel>
2002-03-15 11:51 ` IO delay, port 0x80, and BIOS POST codes Andi Kleen
2002-03-15 12:47 ` Martin Wilck
2002-03-15 12:52 ` Andi Kleen
2002-03-15 17:41 ` [PATCH] Cleanup port 0x80 use (was: Re: IO delay ...) Martin Wilck
2002-03-15 18:05 ` Alan Cox
2002-03-15 20:41 ` H. Peter Anvin
2002-03-15 21:33 ` Linus Torvalds
2002-03-15 21:37 ` Alan Cox
2002-03-16 0:01 ` H. Peter Anvin
2002-03-15 18:57 ` Andreas Dilger
2002-03-15 20:17 ` Martin Wilck
2002-03-17 2:01 ` Jamie Lokier
2002-03-18 9:18 ` Martin Wilck
2002-03-18 9:39 ` Keith Owens [this message]
2002-03-18 11:20 ` Martin Wilck
2002-03-18 15:22 ` Jamie Lokier
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=4463.1016444358@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=Martin.Wilck@fujitsu-siemens.com \
--cc=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
/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®