All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add x86 early-quirks.c file pattern to PCI subsystem
Date: Thu, 8 Nov 2018 17:52:14 -0600	[thread overview]
Message-ID: <20181108235214.GI41183@google.com> (raw)
In-Reply-To: <154041923937.26247.17083948926896599419.stgit@bhelgaas-glaptop.roam.corp.google.com>

On Wed, Oct 24, 2018 at 05:13:59PM -0500, Bjorn Helgaas wrote:
> From: Bjorn Helgaas <bhelgaas@google.com>
> 
> arch/x86/kernel/early-quirks.c contains special PCI quirks that need to
> run even before the usual DECLARE_PCI_FIXUP_EARLY() quirks.  These have
> typically been merged by the x86 maintainers, which is fine, but PCI folks
> should at least see what's happening, so add a file pattern to the PCI
> subsystem entry.
> 
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

I applied this with Ingo's ack to pci/misc for v4.20.

> ---
>  MAINTAINERS |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4ece30f15777..63cb7f3dbbb4 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11249,6 +11249,7 @@ F:	include/uapi/linux/pci*
>  F:	lib/pci*
>  F:	arch/x86/pci/
>  F:	arch/x86/kernel/quirks.c
> +F:	arch/x86/kernel/early-quirks.c
>  
>  PCI NATIVE HOST BRIDGE AND ENDPOINT DRIVERS
>  M:	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> 

      parent reply	other threads:[~2018-11-08 23:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24 22:13 [PATCH] MAINTAINERS: Add x86 early-quirks.c file pattern to PCI subsystem Bjorn Helgaas
2018-10-25  5:40 ` Ingo Molnar
2018-11-08 23:52 ` 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=20181108235214.GI41183@google.com \
    --to=helgaas@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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.