Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>,
	linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH] MAINTAINERS: Include PCI bindings in host bridge entry
Date: Thu, 17 Nov 2022 13:44:13 -0600	[thread overview]
Message-ID: <20221117194413.GA1205039@bhelgaas> (raw)
In-Reply-To: <20221116215337.1032890-1-robh@kernel.org>

On Wed, Nov 16, 2022 at 03:53:37PM -0600, Rob Herring wrote:
> Almost all PCI bindings are controller bindings, so the PCI bindings should
> be listed under the host bridge and endpoint entry.
> 
> Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> Signed-off-by: Rob Herring <robh@kernel.org>

Applied to for-linus for v6.1, thanks!

> ---
> I left the entry under PCI subsystem though just about anything common 
> should end up going to dtschema rather than the kernel. So we could 
> remove it if Bjorn prefers.
> 
>  MAINTAINERS | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c379db61b800..86fe870c3697 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15930,6 +15930,7 @@ Q:	https://patchwork.kernel.org/project/linux-pci/list/
>  B:	https://bugzilla.kernel.org
>  C:	irc://irc.oftc.net/linux-pci
>  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.git
> +F:	Documentation/devicetree/bindings/pci/
>  F:	drivers/pci/controller/
>  F:	drivers/pci/pci-bridge-emul.c
>  F:	drivers/pci/pci-bridge-emul.h
> -- 
> 2.35.1
> 

      reply	other threads:[~2022-11-17 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 21:53 [PATCH] MAINTAINERS: Include PCI bindings in host bridge entry Rob Herring
2022-11-17 19:44 ` 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=20221117194413.GA1205039@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=robh@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