From: "Michael H. Warfield" <mhw@wittsend.com>
To: Herbert Rosmanith <herp@wildsau.idv-edu.uni-linz.ac.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: min() and max() in kernel.h ?
Date: Fri, 17 Aug 2001 15:21:59 -0400 [thread overview]
Message-ID: <20010817152159.A15459@alcove.wittsend.com> (raw)
In-Reply-To: <200108171913.f7HJDKi00416@wildsau.idv-edu.uni-linz.ac.at>
In-Reply-To: <200108171913.f7HJDKi00416@wildsau.idv-edu.uni-linz.ac.at>; from herp@wildsau.idv-edu.uni-linz.ac.at on Fri, Aug 17, 2001 at 09:13:20PM +0200
On Fri, Aug 17, 2001 at 09:13:20PM +0200, Herbert Rosmanith wrote:
> hi,
> just now I tried to compile some module and noticed that it doesnt
> compile anymore because "macro min used with only two arguments".
> I had some "#define min(a,b) (a<b?a:b)" myself.
> I then found min() being defined in <linux/kernel.h> with an additional
> type argument and some superfluos (imo) assignment code. Erm. What's going
> next, drawing elipses in kernel?
> I'm also missing some comment who added min/max to kernel.h, at least
> I want to know who I am going to flame :->
Please review the flamefest threads in this forum going under the
subjects of "2.4.9 does not compile" and related "[PATCH]". That will
answer who what when and why, as well as giving you a suitable case of
characters to throw stones, or whatever else is handy, at.
Rather interesting that Linus ducked out of town just in time
for this... :->
> /herp
Mike
--
Michael H. Warfield | (770) 985-6132 | mhw@WittsEnd.com
(The Mad Wizard) | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
next prev parent reply other threads:[~2001-08-17 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 19:13 min() and max() in kernel.h ? Herbert Rosmanith
2001-08-17 19:21 ` Michael H. Warfield [this message]
2001-08-17 19:26 ` Jeff Golds
2001-08-17 19:29 ` Hua Zhong
2001-08-17 21:52 ` Ingo Oeser
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=20010817152159.A15459@alcove.wittsend.com \
--to=mhw@wittsend.com \
--cc=herp@wildsau.idv-edu.uni-linz.ac.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox