public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Gregory Haskins" <ghaskins@novell•com>
To: Gregory Haskins <gregory.haskins@gmail•com>,
	Randy Dunlap <randy.dunlap@oracle•com>
Cc: sfr@canb•auug.org.au, greg@kroah•com,
	Kamalesh Babulal <kamalesh@linux•vnet.ibm.com>,
	LKML <linux-kernel@vger•kernel.org>,
	linux-next@vger•kernel.org, netdev@vger•kernel.org
Subject: Re: [BUILD-FAILURE] next-20091015 - vbus_enet driver breaks with allmodconfig
Date: Fri, 06 Nov 2009 12:02:41 -0700	[thread overview]
Message-ID: <4AF42C810200005A00058361@sinclair.provo.novell.com> (raw)
In-Reply-To: <20091106093856.e9eac13e.randy.dunlap@oracle.com>

>>> On 11/6/2009 at 12:38 PM, in message
<20091106093856.e9eac13e.randy.dunlap@oracle•com>, Randy Dunlap
<randy.dunlap@oracle•com> wrote: 
> On Thu, 15 Oct 2009 18:25:05 -0400 Gregory Haskins wrote:
> 
>> Randy Dunlap wrote:
>> > On Thu, 15 Oct 2009 13:39:44 -0400 Gregory Haskins wrote:
>> > 
>> >>
>> >> I am having difficulty reproducing the problem.  When I look at the
>> >> Kconfig, I see that VBUS_ENET has a "select VBUS_PROXY" as I would
>> >> expect.  Additionally, if I run allmodconfig I can confirm that I get
>> >> VBUS_ENET=m, VBUS_PROXY=y:
>> > 
>> > Greg,
>> > 
>> > Did you try to reproduce it with the ppc64 config file?
>> > allmodconfig on what arch?
>> > 
>> > I think the problem is that arch/x86/Kconfig says:
>> > 
>> > source "drivers/vbus/Kconfig"
>> > 
>> > and that should actually be in drivers/Kconfig, so that it applies
>> > to ppc64 et al, not just x86.
>> 
>> Ah, indeed.  I only have/tried x86, and that is the issue.  I will have
>> to fix this (and the create_irq() dependency you mention in the next mail).
> 
> Hi Greg,
> 
> I'm still getting
> pci-bridge.c:(.text+0x31b633): undefined reference to `create_irq'
> 
> on today's linux-next-20091106.
> CONFIG_SMP=n
> CONFIG_X86_UP_APIC=n
> 
> full config attached.
> 
> 
> ---
> ~Randy

Indeed.  Looks like I need to be smarter about how the create_irq facility is used.  I will fix this. 

Thanks Randy,
-Greg

  reply	other threads:[~2009-11-06 19:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15  4:25 linux-next: Tree for October 15 Stephen Rothwell
2009-10-15 10:48 ` [BUILD-FAILURE] next-20091015 - vbus_enet driver breaks with allmodconfig Kamalesh Babulal
2009-10-15 11:21   ` Gregory Haskins
2009-10-15 17:39     ` Gregory Haskins
2009-10-15 18:42       ` Randy Dunlap
2009-10-15 18:54         ` Randy Dunlap
2009-10-15 22:25         ` Gregory Haskins
2009-11-06 17:38           ` Randy Dunlap
2009-11-06 19:02             ` Gregory Haskins [this message]
2009-10-16  0:29   ` Gregory Haskins
2009-10-15 19:17 ` linux-next: Tree for October 15 (i7core_edac) Randy Dunlap
2009-10-15 22:29 ` [PATCH -next] vmxnet3: use dev_dbg, fix build for CONFIG_BLOCK=n Randy Dunlap
2009-10-15 22:35   ` [Pv-drivers] " Bhavesh Davda
2009-10-15 22:42     ` Randy Dunlap
2009-10-15 22:47       ` Dmitry Torokhov
2009-10-15 22:53         ` Dmitry Torokhov
2009-10-15 22:53         ` Bhavesh Davda
2009-10-17  0:54     ` David Miller
2009-10-15 22:37   ` Shreyas Bhatewara

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=4AF42C810200005A00058361@sinclair.provo.novell.com \
    --to=ghaskins@novell$(echo .)com \
    --cc=greg@kroah$(echo .)com \
    --cc=gregory.haskins@gmail$(echo .)com \
    --cc=kamalesh@linux$(echo .)vnet.ibm.com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=randy.dunlap@oracle$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /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