From: Grant Likely <grant.likely@secretlab.ca>
To: paulus@samba.org, linuxppc-dev@ozlabs.org, benh@kernel.crashing.org
Subject: [PATCH] Don't build arch/powerpc/sysdev/dcr.c for ARCH=ppc kernels
Date: Wed, 03 Oct 2007 22:50:42 -0600 [thread overview]
Message-ID: <20071004044911.30154.23109.stgit@trillian.cg.shawcable.net> (raw)
From: Grant Likely <grant.likely@secretlab.ca>
dcr.c is an arch/powerpc only thing.
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
---
Ben/Paulus,
As far as I can tell this is correct. Having sysdev/dcr.c in the arch/ppc
build spits out warnings. Grep doesn't show anything in arch/ppc that
is using it.
Cheers,
g.
arch/powerpc/sysdev/Makefile | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/sysdev/Makefile b/arch/powerpc/sysdev/Makefile
index 592c17e..7f88d4e 100644
--- a/arch/powerpc/sysdev/Makefile
+++ b/arch/powerpc/sysdev/Makefile
@@ -6,7 +6,6 @@ mpic-msi-obj-$(CONFIG_PCI_MSI) += mpic_msi.o mpic_u3msi.o
obj-$(CONFIG_MPIC) += mpic.o $(mpic-msi-obj-y)
obj-$(CONFIG_PPC_MPC106) += grackle.o
-obj-$(CONFIG_PPC_DCR) += dcr.o
obj-$(CONFIG_PPC_DCR_NATIVE) += dcr-low.o
obj-$(CONFIG_PPC_PMI) += pmi.o
obj-$(CONFIG_U3_DART) += dart_iommu.o
@@ -31,6 +30,7 @@ endif
# Temporary hack until we have migrated to asm-powerpc
ifeq ($(ARCH),powerpc)
+obj-$(CONFIG_PPC_DCR) += dcr.o
obj-$(CONFIG_CPM2) += cpm2_common.o cpm2_pic.o
obj-$(CONFIG_8xx) += mpc8xx_pic.o commproc.o
obj-$(CONFIG_UCODE_PATCH) += micropatch.o
next reply other threads:[~2007-10-04 4:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 4:50 Grant Likely [this message]
2007-10-04 10:56 ` [PATCH] Don't build arch/powerpc/sysdev/dcr.c for ARCH=ppc kernels Josh Boyer
2007-10-04 11:08 ` Benjamin Herrenschmidt
2007-10-04 12:16 ` Josh Boyer
2007-10-04 14:34 ` Michael Ellerman
2007-10-04 14:42 ` Josh Boyer
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=20071004044911.30154.23109.stgit@trillian.cg.shawcable.net \
--to=grant.likely@secretlab.ca \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 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.