linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alan Stern <stern@rowland.harvard.edu>
Subject: linux-next: build failures after merge of the final tree (usb tree related)
Date: Fri, 2 Nov 2012 17:04:59 +1100	[thread overview]
Message-ID: <20121102170459.5e152727a2a38797ee493da0@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 3396 bytes --]

Hi ,

After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:

In file included from drivers/usb/host/ehci-platform.c:28:0:
drivers/usb/host/ehci.h: In function 'ehci_readl':
drivers/usb/host/ehci.h:662:3: error: implicit declaration of function 'readl_be' [-Werror=implicit-function-declaration]
drivers/usb/host/ehci.h:663:3: error: implicit declaration of function 'readl' [-Werror=implicit-function-declaration]
drivers/usb/host/ehci.h: In function 'ehci_writel':
drivers/usb/host/ehci.h:674:3: error: implicit declaration of function 'writel_be' [-Werror=implicit-function-declaration]
drivers/usb/host/ehci.h:675:3: error: implicit declaration of function 'writel' [-Werror=implicit-function-declaration]

Caused by commit 99f91934a907 ("USB: EHCI: make ehci-platform a separate
driver") from the usb tree.

I have reverted that commit for today.

I then got:

drivers/usb/chipidea/built-in.o: In function `ehci_init_driver':
(.opd+0x5a0): multiple definition of `ehci_init_driver'
drivers/usb/host/built-in.o:(.opd+0xb58): first defined here
drivers/usb/chipidea/built-in.o: In function `.ehci_init_driver':
(.text+0x6528): multiple definition of `.ehci_init_driver'
drivers/usb/host/built-in.o:(.text+0x9eb4): first defined here
drivers/usb/chipidea/built-in.o: In function `ehci_suspend':
(.opd+0xc18): multiple definition of `ehci_suspend'
drivers/usb/host/built-in.o:(.opd+0x11d0): first defined here
drivers/usb/chipidea/built-in.o: In function `ehci_resume':
(.opd+0x1020): multiple definition of `ehci_resume'
drivers/usb/host/built-in.o:(.opd+0x1680): first defined here
drivers/usb/chipidea/built-in.o: In function `.ehci_suspend':
(.text+0x100e4): multiple definition of `.ehci_suspend'
drivers/usb/host/built-in.o:(.text+0x13b00): first defined here
drivers/usb/chipidea/built-in.o: In function `.ehci_resume':
(.text+0x17760): multiple definition of `.ehci_resume'
drivers/usb/host/built-in.o:(.text+0x1b498): first defined here
drivers/usb/chipidea/built-in.o: In function `ehci_setup':
(.opd+0x1128): multiple definition of `ehci_setup'
drivers/usb/host/built-in.o:(.opd+0x17a0): first defined here
drivers/usb/chipidea/built-in.o: In function `.ehci_setup':
(.text+0x228f0): multiple definition of `.ehci_setup'
drivers/usb/host/built-in.o:(.text+0x266fc): first defined here

Which is caused by commit 3e0232039967 ("USB: EHCI: prepare to make
ehci-hcd a library module").

I have added the following patch to disable the chipidea driver for now:

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 2 Nov 2012 16:59:55 +1100
Subject: [PATCH] usb: mark the chipidea broken for now

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 drivers/usb/chipidea/Kconfig |    1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/usb/chipidea/Kconfig b/drivers/usb/chipidea/Kconfig
index 1ea932a..26a239a 100644
--- a/drivers/usb/chipidea/Kconfig
+++ b/drivers/usb/chipidea/Kconfig
@@ -1,6 +1,7 @@
 config USB_CHIPIDEA
 	tristate "ChipIdea Highspeed Dual Role Controller"
 	depends on USB || USB_GADGET
+	depends on BROKEN
 	help
 	  Say Y here if your system has a dual role high speed USB
 	  controller based on ChipIdea silicon IP. Currently, only the
-- 
1.7.10.280.gaa39

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2012-11-02  6:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-02  6:04 Stephen Rothwell [this message]
2012-11-02 19:05 ` linux-next: build failures after merge of the final tree (usb tree related) Greg KH

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=20121102170459.5e152727a2a38797ee493da0@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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).