From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: Suman Anna <s-anna@ti.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Ohad Ben-Cohen <ohad@wizery.com>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-remoteproc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, "Andrew F. Davis" <afd@ti.com>,
Sam Nelson <sam.nelson@ti.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: remoteproc: Add Keystone DSP remoteproc binding
Date: Sat, 10 Jun 2017 12:33:38 -0700 [thread overview]
Message-ID: <3a4d0c88-6077-1c59-8559-d3db3de914f4@oracle.com> (raw)
In-Reply-To: <20170608002447.47580-2-s-anna@ti.com>
On 6/7/2017 5:24 PM, Suman Anna wrote:
> Add the device tree bindings document for the Texas Instrument's
> Keystone 2 DSP remoteproc devices.
>
> Signed-off-by: Suman Anna <s-anna@ti.com>
> Signed-off-by: Sam Nelson <sam.nelson@ti.com>
> ---
> v2 Changes:
> - Modified the patch title
> - Dropped unstable binding status
> - Dropped the 'label' property and replaced the device node description
> to use an alias
> - Renamed 'kick-gpio' to 'kick-gpios'
> - Updated the example
Looks reasonable to me. Ofcourse you need Rob's ack for this one.
Acked-by: Santosh Shilimkar <ssantosh@kernel.org>
next prev parent reply other threads:[~2017-06-10 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 0:24 [PATCH v2 0/3] Add Keystone2 Remoteproc driver Suman Anna
2017-06-08 0:24 ` [PATCH v2 1/3] dt-bindings: remoteproc: Add Keystone DSP remoteproc binding Suman Anna
2017-06-09 14:27 ` Rob Herring
2017-06-10 19:33 ` Santosh Shilimkar [this message]
2017-06-08 0:24 ` [PATCH v2 2/3] remoteproc/keystone: Add a remoteproc driver for Keystone 2 DSPs Suman Anna
2017-06-10 19:32 ` Santosh Shilimkar
2017-06-08 0:24 ` [PATCH v2 3/3] remoteproc/keystone: Ensure the DSPs are in reset in probe Suman Anna
2017-06-10 19:32 ` Santosh Shilimkar
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=3a4d0c88-6077-1c59-8559-d3db3de914f4@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=afd@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=sam.nelson@ti.com \
--cc=ssantosh@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
all inboxes | Powered by JetHome®