From: Andy Whitcroft <apw@shadowen.org>
To: Andrew Morton <akpm@osdl.org>, Nicolas DET <nd@bplan-gmbh.de>
Cc: linux-kernel@vger.kernel.org, Steve Fox <drfickle@us.ibm.com>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@ozlabs.org
Subject: Re: 2.6.19-rc5-mm1 -- ppc64 ohci-hdc.c compile failure
Date: Thu, 09 Nov 2006 15:04:13 +0000 [thread overview]
Message-ID: <4553436D.30601@shadowen.org> (raw)
In-Reply-To: <20061108015452.a2bb40d2.akpm@osdl.org>
We are seeing compile failures on ppc64 in ohci-hcd.c as below:
In file included from drivers/usb/host/ohci-hcd.c:949:
drivers/usb/host/ohci-ppc-of.c: In function `ohci_hcd_ppc_of_init':
drivers/usb/host/ohci-ppc-of.c:272: warning: int format, different type
arg (arg 2)
drivers/usb/host/ohci-ppc-of.c:272: warning: int format, different type
arg (arg 3)
drivers/usb/host/ohci-ppc-of.c: At top level:
drivers/usb/host/ohci-ppc-of.c:282: error: redefinition of `__inittest'
drivers/usb/host/ohci-pci.c:252: error: `__inittest' previously defined here
drivers/usb/host/ohci-ppc-of.c:282: error: redefinition of `init_module'
drivers/usb/host/ohci-pci.c:252: error: `init_module' previously defined
here
drivers/usb/host/ohci-ppc-of.c:283: error: redefinition of `__exittest'
drivers/usb/host/ohci-pci.c:260: error: `__exittest' previously defined here
drivers/usb/host/ohci-ppc-of.c:283: error: redefinition of `cleanup_module'
drivers/usb/host/ohci-pci.c:260: error: `cleanup_module' previously
defined here
Seems that the patch below has introduced USB_OHCI_HCD_PPC_OF enabled by
default. When it and CONFIG_USB_OHCI_HCD_PPC_SOC are enabled which
occured by default on my config then we end up with two module_init()
calls, which is illegal.
powerpc-add-of_platform-support-for-ohci-bigendian-hc
I am guessing that we are only meant to be able to have one of these
defined at a time? I changed the default to n for this and I could at
least compile the kernel, but I am sure thats not the right fix.
Nicolas?
-apw
next prev parent reply other threads:[~2006-11-09 15:04 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 9:54 2.6.19-rc5-mm1 Andrew Morton
2006-11-08 11:11 ` 2.6.19-rc5-mm1 Reuben Farrelly
2006-11-08 20:05 ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-08 20:15 ` 2.6.19-rc5-mm1 Dave Jones
2006-11-08 20:31 ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-08 21:18 ` 2.6.19-rc5-mm1 Dave Jones
2006-11-09 3:09 ` [PATCH] cpufreq: select consistently (Re: 2.6.19-rc5-mm1) Randy Dunlap
2006-11-09 3:39 ` Dave Jones
2006-11-08 12:07 ` 2.6.19-rc5-mm1 Mariusz Kozlowski
2006-11-08 12:32 ` 2.6.19-rc5-mm1 Hesse, Christian
2006-11-08 12:54 ` 2.6.19-rc5-mm1 Mariusz Kozlowski
2006-11-08 14:57 ` 2.6.19-rc5-mm1 Mariusz Kozlowski
2006-11-08 18:13 ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-08 19:19 ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-08 20:47 ` 2.6.19-rc5-mm1 Mariusz Kozlowski
2006-11-08 15:08 ` 2.6.19-rc5-mm1 Benoit Boissinot
2006-11-08 22:10 ` 2.6.19-rc5-mm1 Thomas Gleixner
2006-11-08 23:31 ` 2.6.19-rc5-mm1 Rafael J. Wysocki
2006-11-09 0:17 ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-09 0:44 ` 2.6.19-rc5-mm1 Rafael J. Wysocki
2006-11-09 0:55 ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-09 1:04 ` 2.6.19-rc5-mm1 Rafael J. Wysocki
2006-11-09 15:42 ` 2.6.19-rc5-mm1: HPC nx6325 breakage, VESA fb problem, md-raid problem Rafael J. Wysocki
2006-11-09 17:58 ` Andrew Morton
2006-11-10 4:49 ` Andi Kleen
2006-11-10 5:15 ` Andrew Morton
2006-11-10 6:19 ` Andi Kleen
2006-11-10 11:21 ` Rafael J. Wysocki
2006-11-10 11:51 ` Andi Kleen
2006-11-10 10:44 ` Franck Bui-Huu
2006-11-10 6:28 ` Neil Brown
2006-11-10 23:20 ` Rafael J. Wysocki
2006-11-10 23:29 ` Neil Brown
2006-11-09 15:04 ` Andy Whitcroft [this message]
2006-11-09 22:43 ` 2.6.19-rc5-mm1 -- ppc64 ohci-hdc.c compile failure Benjamin Herrenschmidt
2006-11-10 9:49 ` Paul Mackerras
2006-11-10 9:58 ` Benjamin Herrenschmidt
2006-11-09 18:43 ` 2.6.19-rc5-mm1 Benoit Boissinot
2006-11-09 19:04 ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-09 19:26 ` 2.6.19-rc5-mm1 Mattia Dongili
2006-11-09 21:58 ` [linux-usb-devel] 2.6.19-rc5-mm1 Alan Stern
2006-11-09 22:51 ` Andrew Morton
2006-11-09 23:39 ` Cédric Augonnet
2006-11-10 0:11 ` Andrew Morton
2006-11-10 20:17 ` Anton Vorontsov
2006-11-10 19:29 ` Benoit Boissinot
2006-11-10 3:21 ` 2.6.19-rc5-mm1 Ed Tomlinson
2006-11-10 3:31 ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-10 12:28 ` 2.6.19-rc5-mm1 Ed Tomlinson
2006-11-10 16:29 ` 2.6.19-rc5-mm1 Benoit Boissinot
2006-11-10 16:59 ` 2.6.19-rc5-mm1 Thomas Gleixner
2006-11-10 17:25 ` 2.6.19-rc5-mm1 Benoit Boissinot
2006-11-10 20:20 ` 2.6.19-rc5-mm1 Benoit Boissinot
2006-11-10 20:41 ` 2.6.19-rc5-mm1 Thomas Gleixner
2006-11-13 15:58 ` 2.6.19-rc5-mm1 Mariusz Kozlowski
2006-11-13 22:19 ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-13 22:26 ` 2.6.19-rc5-mm1 Mariusz Kozlowski
2006-11-13 23:37 ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-13 21:03 ` [-mm patch] arch/i386/kernel/apic.c: make a function static Adrian Bunk
2006-11-14 6:54 ` Ingo Molnar
2006-11-13 21:03 ` [-mm patch] make arch/i386/kernel/io_apic.c:timer_irq_works() static again Adrian Bunk
2006-11-13 21:52 ` Zachary Amsden
2006-11-14 6:53 ` Ingo Molnar
2006-11-13 21:03 ` [-mm patch] i386: unexport read_persistent_clock Adrian Bunk
2006-11-13 21:04 ` [-mm patch] make arch/i386/kernel/cpu/common.c:alloc_gdt() static Adrian Bunk
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=4553436D.30601@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@osdl.org \
--cc=drfickle@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=nd@bplan-gmbh.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox