From: Tony Lindgren <tony@atomide.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Lokesh Vutla <lokeshvutla@ti.com>,
Rob Herring <robh+dt@kernel.org>, Sekhar Nori <nsekhar@ti.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>
Subject: Re: [PATCH v3] arm: dts: ti: drop usage of redundant compatible
Date: Fri, 11 Jun 2021 10:27:08 +0300 [thread overview]
Message-ID: <YMMQTIIGneDZfArl@atomide.com> (raw)
In-Reply-To: <b6b1277c-916f-49b9-cc63-1235a0c35b02@ti.com>
* Grygorii Strashko <grygorii.strashko@ti.com> [210601 13:05]:
> On 01/06/2021 08:40, Lokesh Vutla wrote:
> > Commit 229110c1aa691 ("ARM: dts: am437x/am33xx/da850: Add new ECAP and
> > EPWM bindings") added ti,am3352-ehrpwm compatible which is similar to
> > ti,am33xx-ehrpwm but without out t,hwmod properties. But with commit
> > 58bfbea5b1c68 ("ARM: dts: am437x/am33xx: Remove hwmod entries for ECAP
> > and EPWM nodes") dropped support for all ti,hwmod for ehrpwm, but
> > missed deprecating ti,am33xx-ehrpwm compatible. So drop ti,am33xx-ehrpwm
> > from DT as it is no longer needed.
> >
> > ti-ehrpwn driver still support ti,am33xx-ehrpwm in order to maintain
> > backward compatibility.
...
> Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>
Applying into omap-for-v5.14/dt thanks.
Tony
prev parent reply other threads:[~2021-06-11 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 5:40 [PATCH v3] arm: dts: ti: drop usage of redundant compatible Lokesh Vutla
2021-06-01 13:04 ` Grygorii Strashko
2021-06-11 7:27 ` Tony Lindgren [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=YMMQTIIGneDZfArl@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).