All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, X86 ML <x86@kernel.org>,
	lguest@lists.ozlabs.org, Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: linux-next: Tree for Feb 18 (x86)
Date: Wed, 18 Feb 2015 14:45:23 -0800	[thread overview]
Message-ID: <54E51603.8040601@infradead.org> (raw)
In-Reply-To: <54E4DE1C.1020503@infradead.org>

On 02/18/15 10:46, Randy Dunlap wrote:
> On 02/17/15 19:22, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add any material destined for v3.21 to your linux-next
>> included trees until after v3.20-rc1 has been released.
>>
>> Changes since 20150217:
>>
> 
> 
> on i386, when CONFIG_PCI is not enabled:
> 
> arch/x86/built-in.o: In function `early_put_chars':
> boot.c:(.init.text+0x70): undefined reference to `write_pci_config_byte'
> boot.c:(.init.text+0x90): undefined reference to `write_pci_config'
> boot.c:(.init.text+0xb2): undefined reference to `write_pci_config'
> boot.c:(.init.text+0xc7): undefined reference to `write_pci_config'
> boot.c:(.init.text+0xe0): undefined reference to `early_pci_allowed'
> boot.c:(.init.text+0x10a): undefined reference to `read_pci_config'
> boot.c:(.init.text+0x126): undefined reference to `read_pci_config'
> boot.c:(.init.text+0x150): undefined reference to `read_pci_config_byte'
> boot.c:(.init.text+0x17a): undefined reference to `read_pci_config_byte'
> boot.c:(.init.text+0x19c): undefined reference to `read_pci_config_byte'
> boot.c:(.init.text+0x1ba): undefined reference to `read_pci_config_byte'
> boot.c:(.init.text+0x1d8): undefined reference to `read_pci_config'
> boot.c:(.init.text+0x1f6): undefined reference to `read_pci_config'
> boot.c:(.init.text+0x23d): undefined reference to `read_pci_config_byte'
> arch/x86/built-in.o: In function `lguest_init':
> (.init.text+0x5f5): undefined reference to `pcibios_enable_irq'
> arch/x86/built-in.o: In function `lguest_init':
> (.init.text+0x5ff): undefined reference to `pcibios_disable_irq'
> 
> 
> Full randconfig file is attached.
> 

This is all lguest-related.  Looks like LGUEST_GUEST should also
depend on PCI (in arch/x86/lguest/Kconfig).


-- 
~Randy

  reply	other threads:[~2015-02-18 22:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18  3:22 linux-next: Tree for Feb 18 Stephen Rothwell
2015-02-18 18:46 ` linux-next: Tree for Feb 18 (x86) Randy Dunlap
2015-02-18 22:45   ` Randy Dunlap [this message]
     [not found]     ` <54E51603.8040601-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-02-19  2:01       ` Rusty Russell
2015-02-19  2:01         ` Rusty Russell

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=54E51603.8040601@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=lguest@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    --cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.