From: Lokesh Vutla <lokeshvutla@ti.com>
To: <thierry.reding@gmail.com>, <u.kleine-koenig@pengutronix.de>,
<lee.jones@linaro.org>, Rob Herring <robh+dt@kernel.org>
Cc: <tony@atomide.com>, Vignesh R <vigneshr@ti.com>,
Nishanth Menon <nm@ti.com>, <linux-pwm@vger.kernel.org>,
Device Tree Mailing List <devicetree@vger.kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>
Subject: Re: [PATCH 0/2] dt-bindings: pwm: pwm-tiecap: Convert to json schema
Date: Mon, 21 Jun 2021 17:23:33 +0530 [thread overview]
Message-ID: <a84a1fcb-b85d-975f-1763-03cd533855f1@ti.com> (raw)
In-Reply-To: <20210601102804.22152-1-lokeshvutla@ti.com>
Hi Thierry,
On 01/06/21 3:58 pm, Lokesh Vutla wrote:
> This series:
> - converts tiecap to DT schema format using json-schema
> - Add new compatible for AM64 SoC.
If there are no objections, can we merge this series?
Thanks and regards,
Lokesh
>
> Lokesh Vutla (2):
> dt-bindings: pwm: pwm-tiecap: Convert to json schema
> dt-bindings: pwm: pwm-tiecap: Add compatible string for AM64 SoC
>
> .../devicetree/bindings/pwm/pwm-tiecap.txt | 51 ---------------
> .../devicetree/bindings/pwm/pwm-tiecap.yaml | 64 +++++++++++++++++++
> 2 files changed, 64 insertions(+), 51 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/pwm/pwm-tiecap.txt
> create mode 100644 Documentation/devicetree/bindings/pwm/pwm-tiecap.yaml
>
prev parent reply other threads:[~2021-06-21 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 10:28 [PATCH 0/2] dt-bindings: pwm: pwm-tiecap: Convert to json schema Lokesh Vutla
2021-06-01 10:28 ` [PATCH 1/2] " Lokesh Vutla
2021-06-04 21:49 ` Rob Herring
2021-06-01 10:28 ` [PATCH 2/2] dt-bindings: pwm: pwm-tiecap: Add compatible string for AM64 SoC Lokesh Vutla
2021-06-04 21:49 ` Rob Herring
2021-06-21 11:53 ` Lokesh Vutla [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=a84a1fcb-b85d-975f-1763-03cd533855f1@ti.com \
--to=lokeshvutla@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tony@atomide.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vigneshr@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