linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH 35/54] MAINTAINERS: Add file patterns for pci device tree bindings
Date: Fri, 10 Jun 2016 19:06:19 -0500	[thread overview]
Message-ID: <20160611000619.GE16462@localhost> (raw)
In-Reply-To: <1463907991-7916-36-git-send-email-geert@linux-m68k.org>

On Sun, May 22, 2016 at 11:06:12AM +0200, Geert Uytterhoeven wrote:
> Submitters of device tree binding documentation may forget to CC
> the subsystem maintainer if this is missing.
> 
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> Cc: linux-pci@vger.kernel.org

Applied to pci/misc for v4.8, thanks, Geert.

> ---
> Please apply this patch directly if you want to be involved in device
> tree binding documentation for your subsystem.
> ---
>  MAINTAINERS | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 868111d26536f086..2e4bacda7f40a7e8 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8695,6 +8695,7 @@ L:	linux-pci@vger.kernel.org
>  Q:	http://patchwork.ozlabs.org/project/linux-pci/list/
>  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
>  S:	Supported
> +F:	Documentation/devicetree/bindings/pci/
>  F:	Documentation/PCI/
>  F:	drivers/pci/
>  F:	include/linux/pci*
> -- 
> 1.9.1
> 

      reply	other threads:[~2016-06-11  0:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1463907991-7916-1-git-send-email-geert@linux-m68k.org>
2016-05-22  9:06 ` [PATCH 35/54] MAINTAINERS: Add file patterns for pci device tree bindings Geert Uytterhoeven
2016-06-11  0:06   ` 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=20160611000619.GE16462@localhost \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.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).