linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Cort Dougan <cort@fsmlabs.com>
To: tom_gall@vnet.ibm.com
Cc: linuxppc-commit@fsmlabs.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: compiler or kernel source defines
Date: Thu, 12 Apr 2001 15:58:13 -0600	[thread overview]
Message-ID: <20010412155813.I4021@ftsoj.fsmlabs.com> (raw)
In-Reply-To: <3AD5F612.E3E282E8@vnet.ibm.com>; from tom_gall@vnet.ibm.com on Thu, Apr 12, 2001 at 06:38:10PM +0000


I've been steering towards use of CONFIG_PPC which we set in the kernel
config.  I'd like to continue to use that for _all_ PPC's but we could have
CONFIG_PPC32 and CONFIG_PPC64 for each version.

If that'll work for you guys I can add those.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-04-12 21:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-12 18:38 compiler or kernel source defines tom_gall
2001-04-12 21:58 ` Cort Dougan [this message]
2001-04-12 23:23 ` Anton Blanchard

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=20010412155813.I4021@ftsoj.fsmlabs.com \
    --to=cort@fsmlabs.com \
    --cc=linuxppc-commit@fsmlabs.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=tom_gall@vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).