From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Jes Sorensen <jes@trained-monkey.org>,
Anton Altaparmakov <aia21@cam.ac.uk>,
Troy Benjegerdes <hozer@drgw.net>,
wli@holomorphy.com, torvalds@transmeta.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bring sanity to div64.h and do_div usage
Date: Fri, 22 Feb 2002 11:00:49 -0500 [thread overview]
Message-ID: <3C766B31.6922270C@mandrakesoft.com> (raw)
In-Reply-To: <5.1.0.14.2.20020208113710.04ecedf0@pop.cus.cam.ac.uk> <20020207234555.N17426@altus.drgw.net> <5.1.0.14.2.20020208181656.03862ec0@pop.cus.cam.ac.uk> <d37kp5v9y5.fsf@lxplus050.cern.ch> <3C7660F5.FC238A7E@mandrakesoft.com> <15478.25001.512565.628500@trained-monkey.org> <3C76631C.E685815D@mandrakesoft.com> <jepu2xzf26.fsf@sykes.suse.de>
Andreas Schwab wrote:
> If consistency is your goal then CONFIG_I386 should be defined.
I was referring to consistency of having one symbol that can be tested
in most (note: not all) makefiles, C code, and config.in code.
The i386 arch already has CONFIG_X86. I agree that if someone cared to
make define always equal CONFIG_upcase($arch), you are correct.
Jeff
--
Jeff Garzik | "UNIX enhancements aren't."
Building 1024 | -- says /usr/games/fortune
MandrakeSoft |
next prev parent reply other threads:[~2002-02-22 16:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 5:45 [PATCH] bring sanity to div64.h and do_div usage Troy Benjegerdes
2002-02-08 12:15 ` Anton Altaparmakov
2002-02-08 17:57 ` Troy Benjegerdes
2002-02-08 18:49 ` Maciej W. Rozycki
2002-02-08 19:34 ` Anton Altaparmakov
2002-02-08 21:16 ` Troy Benjegerdes
2002-02-15 18:47 ` Updated div64.h cleanup Troy Benjegerdes
2002-02-22 14:59 ` [PATCH] bring sanity to div64.h and do_div usage Jes Sorensen
2002-02-22 15:17 ` Jeff Garzik
2002-02-22 15:20 ` Jes Sorensen
2002-02-22 15:26 ` Jeff Garzik
2002-02-22 15:34 ` Jes Sorensen
2002-02-22 16:05 ` Jeff Garzik
2002-02-22 15:55 ` Andreas Schwab
2002-02-22 16:00 ` Jeff Garzik [this message]
2002-02-22 16:08 ` Nicolas Pitre
2002-02-08 12:29 ` Anton Altaparmakov
2002-02-08 19:04 ` Roman Zippel
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=3C766B31.6922270C@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=aia21@cam.ac.uk \
--cc=hozer@drgw.net \
--cc=jes@trained-monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwab@suse.de \
--cc=torvalds@transmeta.com \
--cc=wli@holomorphy.com \
/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.