[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAL_JsqLpmG1nc4PX0cFfPaUgi2kF_H4c6hGwjfeUYOUWHUBpsQ@mail.gmail.com>
Date: Fri, 13 Mar 2015 10:22:40 -0500
From: Rob Herring <robherring2@...il.com>
To: Matt Porter <mporter@...sulko.com>
Cc: Devicetree List <devicetree@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Pawel Moll <pawel.moll@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Pantelis Antoniou <pantelis.antoniou@...sulko.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] dt: submitting-patches: clarify that DT maintainers are
to be cced on bindings
On Thu, Mar 5, 2015 at 9:53 AM, Matt Porter <mporter@...sulko.com> wrote:
> The exact steps provided for submitting binding patches can be read
> as requiring the bindings to be sent only to the devicetree@...r.kernel.org
> list. Since the DT maintainers would like to be Cced on any binding
> submissions, make this requirement explicit in step 2.
>
> Signed-off-by: Matt Porter <mporter@...sulko.com>
Applied for 4.0. Thanks.
Rob
> ---
> Documentation/devicetree/bindings/submitting-patches.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/submitting-patches.txt b/Documentation/devicetree/bindings/submitting-patches.txt
> index 56742bc..7d44eae 100644
> --- a/Documentation/devicetree/bindings/submitting-patches.txt
> +++ b/Documentation/devicetree/bindings/submitting-patches.txt
> @@ -12,6 +12,9 @@ I. For patch submitters
>
> devicetree@...r.kernel.org
>
> + and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify
> + all of the DT maintainers.
> +
> 3) The Documentation/ portion of the patch should come in the series before
> the code implementing the binding.
>
> --
> 1.8.4
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists