From: Jes Sorensen <jes@sunsite.dk>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: 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: 22 Feb 2002 15:59:46 +0100 [thread overview]
Message-ID: <d37kp5v9y5.fsf@lxplus050.cern.ch> (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.20020208113710.04ecedf0@pop.cus.cam.ac.uk> <5.1.0.14.2.20020208181656.03862ec0@pop.cus.cam.ac.uk>
In-Reply-To: Anton Altaparmakov's message of "Fri, 08 Feb 2002 19:34:07 +0000"
Anton Altaparmakov <aia21@cam.ac.uk> writes:
> At 17:57 08/02/02, Troy Benjegerdes wrote:
> >Well, there's a reason I left out CONFIG_M68K deps.. Go tell me where
> >CONFIG_M68K is defined.. ;)
>
> Appologies, it's in Configure.help but that is not a too useful places to
> have it. However the kernel seems to be using:
>
> #if defined(__mc68000__) so just use that instead. Any m68k people reading
> this care to comment?
__mc68000__ is the correct define, I don't know who put in CONFIG_M68K
but it doesn't belong there.
Jes
next prev parent reply other threads:[~2002-02-22 15: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 ` Jes Sorensen [this message]
2002-02-22 15:17 ` [PATCH] bring sanity to div64.h and do_div usage 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
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=d37kp5v9y5.fsf@lxplus050.cern.ch \
--to=jes@sunsite.dk \
--cc=aia21@cam.ac.uk \
--cc=hozer@drgw.net \
--cc=linux-kernel@vger.kernel.org \
--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.