linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@freescale.com>
To: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: building ppc_htab?
Date: Wed, 16 Mar 2005 00:57:24 -0600	[thread overview]
Message-ID: <4e44f753c3a197eff3b584f24a239f06@freescale.com> (raw)

Is there any reason not to make the following change so we build 
ppc_htab only on PPC STD MMU?  This would also require fixing up 
fs/proc/proc_misc.c.

--- 1.52/arch/ppc/kernel/Makefile       2005-03-13 17:29:44 -06:00
+++ edited/Makefile     2005-03-16 00:44:17 -06:00
@@ -2,7 +2,7 @@
  # Makefile for the linux kernel.
  #

-extra-$(CONFIG_PPC_STD_MMU)    := head.o
+extra-$(CONFIG_PPC_STD_MMU)    := head.o ppc_htab.o
  extra-$(CONFIG_40x)            := head_4xx.o
  extra-$(CONFIG_44x)            := head_44x.o
  extra-$(CONFIG_E500)           := head_e500.o
@@ -14,7 +14,7 @@
  obj-y                          := entry.o traps.o irq.o idle.o time.o 
misc.o \
                                         process.o signal.o ptrace.o 
align.o \
                                         semaphore.o syscalls.o setup.o \
-                                       cputable.o ppc_htab.o perfmon.o
+                                       cputable.o perfmon.o
  obj-$(CONFIG_6xx)              += l2cr.o cpu_setup_6xx.o
  obj-$(CONFIG_SOFTWARE_SUSPEND) += swsusp.o
  obj-$(CONFIG_POWER4)           += cpu_setup_power4.o

- kumar

             reply	other threads:[~2005-03-16  6:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16  6:57 Kumar Gala [this message]
2005-03-16 17:12 ` building ppc_htab? Dan Malek
2005-03-16 22:11 ` Tom Rini
2005-03-17 17:34   ` Kumar Gala
2005-03-17 17:41     ` Tom Rini
2005-03-17 21:58       ` Tom Rini
2005-03-18  5:12         ` Kumar Gala

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=4e44f753c3a197eff3b584f24a239f06@freescale.com \
    --to=kumar.gala@freescale.com \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).