LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 0/3] Documentation: DT bindings: update DT binding docs with Tegra chips
Date: Tue, 3 Feb 2015 20:36:32 -0600 [thread overview]
Message-ID: <CAL_Jsq+rq1Apna4P1YkcsPYhz4dnd7mKHvWXcb663+XYFGV1uQ@mail.gmail.com> (raw)
In-Reply-To: <20150130221104.4761.50643.stgit@dusk.lan>
On Fri, Jan 30, 2015 at 4:11 PM, Paul Walmsley <paul@pwsan.com> wrote:
>
> Update some of the DT binding documentation text files, per Mark's
> comments at:
>
> http://marc.info/?l=linux-tegra&m=142201349727836&w=2
>
> The primary goal with this series is to avoid checkpatch.pl warnings
> and align to the policy that Mark described. This series also updates
> Documentation/devicetree/bindings/submitting-patches.txt to formally
> document this policy.
>
> These patches apply on next-20150123.
>
> This second version incorporates some revisions based on feedback from
> Rob Herring.
Looks good. I've applied the series.
Rob
prev parent reply other threads:[~2015-02-04 2:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 22:11 Paul Walmsley
2015-01-30 22:11 ` [PATCH v2 3/3] Documentation: DT bindings: add nvidia, tegra132-denver compatible string Paul Walmsley
2015-01-30 22:11 ` [PATCH v2 1/3] Documentation: DT: document compatible string existence requirement Paul Walmsley
2015-01-30 22:11 ` [PATCH v2 2/3] Documentation: DT bindings: add more Tegra chip compatible strings Paul Walmsley
2015-01-31 19:28 ` Eduardo Valentin
2015-02-05 19:25 ` Wolfram Sang
2015-02-04 2:36 ` Rob Herring [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=CAL_Jsq+rq1Apna4P1YkcsPYhz4dnd7mKHvWXcb663+XYFGV1uQ@mail.gmail.com \
--to=robherring2@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=paul@pwsan.com \
--cc=robh+dt@kernel.org \
--subject='Re: [PATCH v2 0/3] Documentation: DT bindings: update DT binding docs with Tegra chips' \
/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
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).