From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-pci <linux-pci@vger.kernel.org>
Subject: Re: linux-next: Tree for Feb 3 (arch/x86/{various}; all PCI-related)
Date: Mon, 3 Feb 2020 08:27:31 -0800 [thread overview]
Message-ID: <b569f6f3-a757-5bbb-3e1a-9d78b12709b7@infradead.org> (raw)
In-Reply-To: <20200203142334.4f699874@canb.auug.org.au>
On 2/2/20 7:23 PM, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v5.7 material to your linux-next included
> branches until after v5.6-rc1 has been released.
>
> News: I have added an htmldocs build to the end of my day. It seems to
> be building at the moment, but has many warnings.
>
> Changes since 20200131:
>
(trying this again, with more Cc:s since last week's report [on Jan. 28]
got no response)
on x86_64:
# CONFIG_PCI is not set
Several source files will not build when CONFIG_PCI is not set/enabled.
Examples:
CC arch/x86/events/amd/ibs.o
In file included from ../include/linux/pci.h:1778:0,
from ../arch/x86/events/amd/ibs.c:12:
../arch/x86/include/asm/pci.h: In function '__pcibus_to_node':
../arch/x86/include/asm/pci.h:126:9: error: implicit declaration of function 'to_pci_sysdata'; did you mean 'to_pci_dev'? [-Werror=implicit-function-declaration]
return to_pci_sysdata(bus)->node;
^~~~~~~~~~~~~~
to_pci_dev
../arch/x86/include/asm/pci.h:126:28: error: invalid type argument of '->' (have 'int')
return to_pci_sysdata(bus)->node;
^~
CC arch/x86/kernel/cpu/cacheinfo.o
In file included from ../include/linux/pci.h:1778:0,
from ../arch/x86/kernel/cpu/cacheinfo.c:17:
../arch/x86/include/asm/pci.h: In function '__pcibus_to_node':
../arch/x86/include/asm/pci.h:126:9: error: implicit declaration of function 'to_pci_sysdata'; did you mean 'to_pci_bus'? [-Werror=implicit-function-declaration]
return to_pci_sysdata(bus)->node;
^~~~~~~~~~~~~~
to_pci_bus
../arch/x86/include/asm/pci.h:126:28: error: invalid type argument of '->' (have 'int')
return to_pci_sysdata(bus)->node;
^~
CC arch/x86/kernel/apic/io_apic.o
In file included from ../include/linux/pci.h:1778:0,
from ../arch/x86/kernel/apic/io_apic.c:40:
../arch/x86/include/asm/pci.h: In function '__pcibus_to_node':
../arch/x86/include/asm/pci.h:126:9: error: implicit declaration of function 'to_pci_sysdata'; did you mean 'to_pci_bus'? [-Werror=implicit-function-declaration]
return to_pci_sysdata(bus)->node;
^~~~~~~~~~~~~~
to_pci_bus
../arch/x86/include/asm/pci.h:126:28: error: invalid type argument of '->' (have 'int')
return to_pci_sysdata(bus)->node;
^~
CC arch/x86/kernel/setup.o
In file included from ../include/linux/pci.h:1778:0,
from ../arch/x86/kernel/setup.c:16:
../arch/x86/include/asm/pci.h: In function '__pcibus_to_node':
../arch/x86/include/asm/pci.h:126:9: error: implicit declaration of function 'to_pci_sysdata'; did you mean 'to_pci_bus'? [-Werror=implicit-function-declaration]
return to_pci_sysdata(bus)->node;
^~~~~~~~~~~~~~
to_pci_bus
../arch/x86/include/asm/pci.h:126:28: error: invalid type argument of '->' (have 'int')
return to_pci_sysdata(bus)->node;
^~
CC arch/x86/kernel/x86_init.o
In file included from ../include/linux/pci.h:1778:0,
from ../arch/x86/kernel/x86_init.c:9:
../arch/x86/include/asm/pci.h: In function '__pcibus_to_node':
../arch/x86/include/asm/pci.h:126:9: error: implicit declaration of function 'to_pci_sysdata'; did you mean 'to_pci_bus'? [-Werror=implicit-function-declaration]
return to_pci_sysdata(bus)->node;
^~~~~~~~~~~~~~
to_pci_bus
../arch/x86/include/asm/pci.h:126:28: error: invalid type argument of '->' (have 'int')
return to_pci_sysdata(bus)->node;
^~
CC arch/x86/kernel/irqinit.o
In file included from ../include/linux/pci.h:1778:0,
from ../arch/x86/include/asm/prom.h:15,
from ../arch/x86/kernel/irqinit.c:29:
../arch/x86/include/asm/pci.h: In function '__pcibus_to_node':
../arch/x86/include/asm/pci.h:126:9: error: implicit declaration of function 'to_pci_sysdata'; did you mean 'to_pci_dev'? [-Werror=implicit-function-declaration]
return to_pci_sysdata(bus)->node;
^~~~~~~~~~~~~~
to_pci_dev
../arch/x86/include/asm/pci.h:126:28: error: invalid type argument of '->' (have 'int')
return to_pci_sysdata(bus)->node;
^~
That's just a sample:
$ buildsummary.pl build-r9671.out
file: arch/x86/boot/header.S: errors: 1, warnings: 0
file: arch/x86/include/asm/pci.h: errors: 234, warnings: 0
build-r9671.out: totals: error/warning files: 2, errors: 235, warnings: 0, Section mismatches: 0
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
prev parent reply other threads:[~2020-02-03 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 3:23 linux-next: Tree for Feb 3 Stephen Rothwell
2020-02-03 16:27 ` Randy Dunlap [this message]
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=b569f6f3-a757-5bbb-3e1a-9d78b12709b7@infradead.org \
--to=rdunlap@infradead.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--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 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).