public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	PCI <linux-pci@vger.kernel.org>, X86 ML <x86@kernel.org>,
	lkft-triage@lists.linaro.org
Subject: Re: [next] pci_x86.h:105:8: error: unknown type name 'raw_spinlock_t'
Date: Mon, 14 Mar 2022 11:01:54 -0500	[thread overview]
Message-ID: <20220314160154.GA501271@bhelgaas> (raw)
In-Reply-To: <CA+G9fYtX3RzYbpZRAktPNfbP51obcBi=_PJZ6RT-x+BnE-9ESQ@mail.gmail.com>

On Mon, Mar 14, 2022 at 03:48:12PM +0530, Naresh Kamboju wrote:
> Linux next-20220310 i386 build failed due to below warnings / errors.
> 
>   CC      arch/x86/kernel/resource.o
> In file included from arch/x86/kernel/resource.c:4:0:
> arch/x86/include/asm/pci_x86.h:105:8: error: unknown type name 'raw_spinlock_t'

I don't know what to do with this.  It works for me:

  $ gsr
  71941773e143 ("Add linux-next specific files for 20220310")
  $ ARCH=i386 make defconfig
  $ ARCH=i386 make arch/x86/kernel/resource.o
    ...
    CC      arch/x86/kernel/resource.o
  $ echo $?
  0

What config did you use?  How can I reproduce this?

>  extern raw_spinlock_t pci_config_lock;
>         ^~~~~~~~~~~~~~
> arch/x86/include/asm/pci_x86.h:141:20: error: expected '=', ',', ';',
> 'asm' or '__attribute__' before 'dmi_check_pciprobe'
>  extern void __init dmi_check_pciprobe(void);
>                     ^~~~~~~~~~~~~~~~~~
> arch/x86/include/asm/pci_x86.h:142:20: error: expected '=', ',', ';',
> 'asm' or '__attribute__' before 'dmi_check_skip_isa_align'
>  extern void __init dmi_check_skip_isa_align(void);
>                     ^~~~~~~~~~~~~~~~~~~~~~~~
> arch/x86/include/asm/pci_x86.h:146:19: error: expected '=', ',', ';',
> 'asm' or '__attribute__' before 'pci_acpi_init'
>  extern int __init pci_acpi_init(void);
>                    ^~~~~~~~~~~~~
> arch/x86/include/asm/pci_x86.h:153:20: error: expected '=', ',', ';',
> 'asm' or '__attribute__' before 'pcibios_irq_init'
>  extern void __init pcibios_irq_init(void);
>                     ^~~~~~~~~~~~~~~~
> arch/x86/include/asm/pci_x86.h:154:19: error: expected '=', ',', ';',
> 'asm' or '__attribute__' before 'pcibios_init'
>  extern int __init pcibios_init(void);
>                    ^~~~~~~~~~~~
> arch/x86/include/asm/pci_x86.h:174:19: error: expected '=', ',', ';',
> 'asm' or '__attribute__' before 'pci_mmcfg_arch_init'
>  extern int __init pci_mmcfg_arch_init(void);
>                    ^~~~~~~~~~~~~~~~~~~
> arch/x86/include/asm/pci_x86.h:175:20: error: expected '=', ',', ';',
> 'asm' or '__attribute__' before 'pci_mmcfg_arch_free'
>  extern void __init pci_mmcfg_arch_free(void);
>                     ^~~~~~~~~~~~~~~~~~~
> arch/x86/include/asm/pci_x86.h:182:40: error: expected '=', ',', ';',
> 'asm' or '__attribute__' before 'pci_mmconfig_add'
>  extern struct pci_mmcfg_region *__init pci_mmconfig_add(int segment, int start,
>                                         ^~~~~~~~~~~~~~~~
>   CC      net/core/filter.o
> make[2]: *** [scripts/Makefile.build:288: arch/x86/kernel/resource.o] Error 1
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> 
> --
> Linaro LKFT
> https://lkft.linaro.org
> [1]  https://ci.linaro.org/view/lkft/job/openembedded-lkft-linux-next/DISTRO=lkft,MACHINE=intel-core2-32,label=docker-buster-lkft/1207/consoleText

  reply	other threads:[~2022-03-14 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 10:18 [next] pci_x86.h:105:8: error: unknown type name 'raw_spinlock_t' Naresh Kamboju
2022-03-14 16:01 ` Bjorn Helgaas [this message]
2022-03-14 19:46   ` Randy Dunlap

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=20220314160154.GA501271@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=mingo@redhat.com \
    --cc=naresh.kamboju@linaro.org \
    --cc=rdunlap@infradead.org \
    --cc=tglx@linutronix.de \
    --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