linux-kernel - Re: linux-next: build failure after merge of the pci-current tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 7 Jul 2011 08:52:05 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Ram Pai <linuxram@...ibm.com>
Subject: Re: linux-next: build failure after merge of the pci-current tree

On Thu, 7 Jul 2011 10:58:23 +1000
Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi Jesse,
> 
> After merging the pci-current tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
> 
> drivers/built-in.o:(.toc1+0xb98): undefined reference to `pci_realloc'
> 
> Caused by commit 72007d2b4797 ("PCI: conditional resource-reallocation
> through kernel parameter pci=realloc").
> 
> I have used the pci-current tree from next-20110706 for today.

Oops, x86 bits used in common code.  I've pushed a fix that just moves
the variable into setup-bus.c rather than x86/pci/common.c.

Ram, did you see the microblaze patch I forwarded you?  It moves some
re-alloc control flags into common code; for -next it might be cleaner
to use them in a few places.  Any comments?

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/