Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH -next?] x86: PCI: asm/pci_x86.h needs more #includes
Date: Mon, 14 Mar 2022 14:54:53 -0500	[thread overview]
Message-ID: <20220314195453.GA527280@bhelgaas> (raw)
In-Reply-To: <20220226213703.24041-1-rdunlap@infradead.org>

On Sat, Feb 26, 2022 at 01:37:03PM -0800, Randy Dunlap wrote:
> <asm/pci_x86.h> uses EINVAL, __init, and raw_spinlock_t, so it
> should #include the appropriate files to prevent build errors.
> 
> ../arch/x86/include/asm/pci_x86.h:150:10: error: ‘EINVAL’ undeclared (first use in this function)
>   return -EINVAL;
> 
> ../arch/x86/include/asm/pci_x86.h:105:8: error: unknown type name ‘raw_spinlock_t’
>  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);
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>

Thanks, applied to pci/misc for v5.18.

> Cc: Mark Brown <broonie@kernel.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: Dave Hansen <dave.hansen@linux.intel.com>
> Cc: x86@kernel.org
> Cc: linux-pci@vger.kernel.org
> ---
> Without this patch, I am seeing *many* build errors in
> linux-next-20220225.
> 
> I don't know why this showed up in linux-next-20220225 all of a
> sudden.
> 
>  arch/x86/include/asm/pci_x86.h |    3 +++
>  1 file changed, 3 insertions(+)
> 
> --- linux-next-20220225.orig/arch/x86/include/asm/pci_x86.h
> +++ linux-next-20220225/arch/x86/include/asm/pci_x86.h
> @@ -5,7 +5,10 @@
>   *	(c) 1999 Martin Mares <mj@ucw.cz>
>   */
>  
> +#include <linux/errno.h>
> +#include <linux/init.h>
>  #include <linux/ioport.h>
> +#include <linux/spinlock.h>
>  
>  #undef DEBUG
>  

      reply	other threads:[~2022-03-14 19:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-26 21:37 [PATCH -next?] x86: PCI: asm/pci_x86.h needs more #includes Randy Dunlap
2022-03-14 19:54 ` Bjorn Helgaas [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=20220314195453.GA527280@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bp@alien8.de \
    --cc=broonie@kernel.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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