From: Randy Dunlap <randy.dunlap@oracle•com>
To: akpm <akpm@linux-foundation•org>, lkml <linux-kernel@vger•kernel.org>
Cc: linux-next@vger•kernel.org, david.vrabel@csr•com, greg@kroah•com
Subject: Re: uwb build errors: CONFIG_PCI=n, CONFIG_USB=y
Date: Wed, 14 May 2008 13:17:49 -0700 [thread overview]
Message-ID: <20080514131749.17675ba0.randy.dunlap@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0805061356150.17702@shark.he.net>
[dropped closed list: linux-uwb@bughost•org]
This build error has now moved into 2.6.26-rc2-mm1 also.
On Tue, 6 May 2008 13:58:22 -0700 (PDT) Randy.Dunlap wrote:
>
> On x86_64 or i386, maybe others:
>
> In file included from /home/rdunlap/linsrc/next-20080506/drivers/uwb/umc-bus.c:12:
> /home/rdunlap/linsrc/next-20080506/include/linux/uwb/umc.h: In function 'umc_parent_pci_dev':
> /home/rdunlap/linsrc/next-20080506/include/linux/uwb/umc.h:145: error: 'pci_bus_type' undeclared (first use in this function)
> /home/rdunlap/linsrc/next-20080506/include/linux/uwb/umc.h:145: error: (Each undeclared identifier is reported only once
> /home/rdunlap/linsrc/next-20080506/include/linux/uwb/umc.h:145: error: for each function it appears in.)
> /home/rdunlap/linsrc/next-20080506/drivers/uwb/umc-bus.c: In function 'umc_match_pci_id':
> /home/rdunlap/linsrc/next-20080506/drivers/uwb/umc-bus.c:29: error: 'pci_bus_type' undeclared (first use in this function)
> /home/rdunlap/linsrc/next-20080506/drivers/uwb/umc-bus.c:33: error: implicit declaration of function 'pci_match_id'
> make[3]: *** [drivers/uwb/umc-bus.o] Error 1
> make[2]: *** [drivers/uwb] Error 2
---
~Randy
next parent reply other threads:[~2008-05-14 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0805061356150.17702@shark.he.net>
2008-05-14 20:17 ` Randy Dunlap [this message]
2008-05-14 21:33 ` uwb build errors: CONFIG_PCI=n, CONFIG_USB=y 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=20080514131749.17675ba0.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=david.vrabel@csr$(echo .)com \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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