linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Greg KH <greg@kroah.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org,
	Sarah Sharp <sarah.a.sharp@linux.intel.com>
Subject: Re: linux-next: usb tree build failure
Date: Thu, 30 Apr 2009 09:27:36 -0700	[thread overview]
Message-ID: <49F9D178.8050706@oracle.com> (raw)
In-Reply-To: <20090430161341.GC18495@kroah.com>

Greg KH wrote:
> On Wed, Apr 29, 2009 at 10:53:30AM -0700, Randy Dunlap wrote:
>> Greg KH wrote:
>>> On Wed, Apr 29, 2009 at 08:44:47AM -0700, Randy Dunlap wrote:
>>>> Greg KH wrote:
>>>>> On Wed, Apr 29, 2009 at 08:18:20AM -0700, Randy Dunlap wrote:
>>>>>> Stephen Rothwell wrote:
>>>>>>> Hi Greg,
>>>>>>>
>>>>>>> Today's linux-next build (powerpc allyesconfig) failed like this:
>>>>>>>
>>>>>>> drivers/usb/built-in.o: In function `.handle_event':
>>>>>>> (.text+0x67dd0): multiple definition of `.handle_event'
>>>>>>> drivers/pcmcia/built-in.o:(.text+0xcfcc): first defined here
>>>>>>> drivers/usb/built-in.o: In function `handle_event':
>>>>>>> (.opd+0x5bc8): multiple definition of `handle_event'
>>>>>>> drivers/pcmcia/built-in.o:(.opd+0xed0): first defined here
>>>>>> There's also this one:
>>>>>>
>>>>>> drivers/usb/host/xhci-mem.c:46: error: implicit declaration of function 'dma_pool_alloc'
>>>>>> drivers/usb/host/xhci-mem.c:69: error: implicit declaration of function 'dma_pool_free'
>>>>>> drivers/usb/host/xhci-mem.c:578: error: implicit declaration of function 'dma_pool_destroy'
>>>>>> drivers/usb/host/xhci-mem.c:657: error: implicit declaration of function 'dma_pool_create'
>>>>>>
>>>>>> That file needs to
>>>>>> #include <linux/dmapool.h>
>>>>> What arch had this problem?
>>>> i386
>>> I can't duplicate this here, care to attach a .config?
>> attached.  But you don't need to be able to duplicate it.
>>
>> The source file obviously uses those interfaces, so it should
>> include that header file.
> 
> Ah, it's a PCI config issue, a Kbuild change will fix this.

So I noticed, but it should still #include the header file since those
interfaces are used.


-- 
~Randy

  reply	other threads:[~2009-04-30 16:26 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29  7:17 linux-next: usb tree build failure Stephen Rothwell
2009-04-29 14:15 ` Greg KH
2009-04-29 15:00   ` Stephen Rothwell
2009-04-29 15:16     ` Greg KH
2009-04-29 15:18 ` Randy Dunlap
2009-04-29 15:37   ` Greg KH
2009-04-29 15:44     ` Randy Dunlap
2009-04-29 17:44       ` Greg KH
2009-04-29 17:53         ` Randy Dunlap
2009-04-30 16:13           ` Greg KH
2009-04-30 16:27             ` Randy Dunlap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-02-02  6:10 Stephen Rothwell
2010-02-02 13:53 ` Greg KH
2010-02-02 22:33   ` Stephen Rothwell
2009-08-19  8:34 Stephen Rothwell
2009-08-19 13:52 ` Greg KH
2009-08-19 23:45   ` Greg KH
2009-08-19 23:58     ` Stephen Rothwell
2008-12-22  0:33 Stephen Rothwell
2008-12-22  1:31 ` Greg KH
2008-12-22  2:42   ` Stephen Rothwell
2008-12-22  6:45     ` Sam Ravnborg
2008-12-22 17:26       ` Inaky Perez-Gonzalez
2008-12-22 17:53         ` Sam Ravnborg
2008-12-22 23:37           ` Inaky Perez-Gonzalez
2008-12-23  4:31             ` Greg KH
2008-12-23  4:30           ` Greg KH
2008-12-23  4:31         ` Greg KH
2008-12-23 10:26           ` Inaky Perez-Gonzalez
2008-12-23 17:17             ` Greg KH
2008-12-24  1:07               ` Inaky Perez-Gonzalez
2009-01-05  4:34                 ` Greg KH
2009-01-05  5:55                   ` Stephen Rothwell
2008-12-29  3:55 ` Stephen Rothwell
2009-01-02  7:27   ` Greg KH
2009-01-03  4:33     ` Stephen Rothwell
2008-11-03  0:36 Stephen Rothwell
2008-11-05  4:47 ` Greg KH
2008-11-05 18:19   ` Mauro Carvalho Chehab
2008-10-14  4:08 Stephen Rothwell
2008-10-14  5:51 ` Alexey Klimov
2008-10-14 17:41   ` Alexey Klimov
2008-10-14 17:26     ` Mauro Carvalho Chehab
2008-10-14  3:59 Stephen Rothwell
2008-10-14  8:24 ` Dmitry
2008-10-14 15:42   ` Dmitry
2008-10-16 16:05 ` Greg KH
2008-10-16 17:27   ` Dmitry Baryshkov
2008-10-16 21:36   ` Dmitry Baryshkov
2008-10-17  0:26     ` Stephen Rothwell
2008-10-17  0:41       ` Dmitry
2008-10-20 18:45         ` Greg KH
2008-08-13  6:37 Stephen Rothwell
2008-08-13  7:33 ` Stephen Rothwell
2008-08-13 14:23   ` Stephen Rothwell
2008-08-14  6:28     ` Stephen Rothwell
2008-08-14  6:54       ` Stephen Rothwell
2008-08-14 12:25         ` Greg KH
2008-08-15  0:16           ` Stephen Rothwell
2008-07-18  1:31 Stephen Rothwell

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=49F9D178.8050706@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=greg@kroah.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=sfr@canb.auug.org.au \
    /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).