From: Sinthu Raja <sinthu.raja@mistralsolutions.com>
To: Suman Anna <s-anna@ti.com>, Rob Herring <robh+dt@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Ohad Ben-Cohen <ohad@wizery.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-remoteproc@vger.kernel.org, Nishanth Menon <nm@ti.com>,
Sinthu Raja <sinthu.raja@ti.com>
Subject: [PATCH V4 0/2] dt-bindings: remoteproc: k3-r5f|dsp: Remove
Date: Mon, 27 Sep 2021 16:08:09 +0530 [thread overview]
Message-ID: <20210927103811.11222-1-sinthu.raja@ti.com> (raw)
From: Sinthu Raja <sinthu.raja@ti.com>
Hi All,
The series of patches are meant to help make the rproc bindings for K3
r5f and dsp support independent of board/platform involved.
Changes in V4:
Addressed review comments:
- Removed Fixes tags from the commit descriptions.
- Updated subject and commit description to emphasis on cleaning up of the
example to address the dt_binding_check warnings.
V3: https://lore.kernel.org/all/20210917095426.19277-1-sinthu.raja@ti.com/
V2: https://lore.kernel.org/all/20210818074030.1877-1-sinthu.raja@ti.com/
V1: https://lore.kernel.org/all/20210817152005.21575-1-sinthu.raja@ti.com/
Sinthu Raja (2):
dt-bindings: remoteproc: k3-r5f: Cleanup SoC compatible from DT
example
dt-bindings: remoteproc: k3-dsp: Cleanup SoC compatible from DT
example
.../devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml | 4 +---
.../devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml | 4 +---
2 files changed, 2 insertions(+), 6 deletions(-)
--
2.31.1
next reply other threads:[~2021-09-27 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 10:38 Sinthu Raja [this message]
2021-09-27 10:38 ` [PATCH V4 1/2] dt-bindings: remoteproc: k3-r5f: Cleanup SoC compatible from DT example Sinthu Raja
2021-09-27 10:38 ` [PATCH V4 2/2] dt-bindings: remoteproc: k3-dsp: " Sinthu Raja
2021-09-27 15:08 ` [PATCH V4 0/2] dt-bindings: remoteproc: k3-r5f|dsp: Remove Nishanth Menon
2021-09-27 17:23 ` Mathieu Poirier
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=20210927103811.11222-1-sinthu.raja@ti.com \
--to=sinthu.raja@mistralsolutions.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=mathieu.poirier@linaro.org \
--cc=nm@ti.com \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=sinthu.raja@ti.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).