From: Rob Herring <robh+dt@kernel.org>
To: Anup Patel <anup.patel@broadcom.com>
Cc: Jassi Brar <jassisinghbrar@gmail.com>,
Mark Rutland <mark.rutland@arm.com>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Pramod KUMAR <pramod.kumar@broadcom.com>,
Rob Rice <rob.rice@broadcom.com>,
"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>,
"bcm-kernel-feedback-list@broadcom.com"
<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH v4 2/2] dt-bindings: Add DT bindings info for FlexRM ring manager
Date: Thu, 5 Jan 2017 10:32:13 -0600 [thread overview]
Message-ID: <CAL_JsqLQn6yGa5J2ctbJhFR5UwC8uX7fHhxDuzLYUOQ4G4Fj2g@mail.gmail.com> (raw)
In-Reply-To: <1483614475-3442-3-git-send-email-anup.patel@broadcom.com>
On Thu, Jan 5, 2017 at 5:07 AM, Anup Patel <anup.patel@broadcom.com> wrote:
> This patch adds device tree bindings document for the FlexRM
> ring manager found on Broadcom iProc SoCs.
>
> Reviewed-by: Ray Jui <ray.jui@broadcom.com>
> Reviewed-by: Scott Branden <scott.branden@broadcom.com>
> Signed-off-by: Anup Patel <anup.patel@broadcom.com>
> ---
> .../bindings/mailbox/brcm,iproc-flexrm-mbox.txt | 59 ++++++++++++++++++++++
> 1 file changed, 59 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mailbox/brcm,iproc-flexrm-mbox.txt
Acked-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2017-01-05 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 11:07 [PATCH v4 0/2] Broadcom FlexRM ring manager support Anup Patel
2017-01-05 11:07 ` [PATCH v4 1/2] mailbox: Add driver for Broadcom FlexRM ring manager Anup Patel
2017-01-19 3:15 ` Anup Patel
2017-01-19 21:23 ` Scott Branden
2017-01-05 11:07 ` [PATCH v4 2/2] dt-bindings: Add DT bindings info for " Anup Patel
2017-01-05 16:32 ` 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_JsqLQn6yGa5J2ctbJhFR5UwC8uX7fHhxDuzLYUOQ4G4Fj2g@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=anup.patel@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pramod.kumar@broadcom.com \
--cc=rjui@broadcom.com \
--cc=rob.rice@broadcom.com \
--cc=sbranden@broadcom.com \
/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).