From: Tony Lindgren <tony@atomide.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
Aswath Govindraju <a-govindraju@ti.com>
Subject: Re: [PATCH v2 0/5] dt-bindings: gpio: omap: Convert to json-schema
Date: Thu, 27 May 2021 15:01:21 +0300 [thread overview]
Message-ID: <YK+KEYncDc6pCb1X@atomide.com> (raw)
In-Reply-To: <2dbbf0f1-be2c-de11-8ffd-77a06688a83d@ti.com>
* Grygorii Strashko <grygorii.strashko@ti.com> [210526 10:06]:
> Hi Tony, Linus, Bartosz,
>
> On 25/05/2021 20:58, Grygorii Strashko wrote:
> > Hi
> >
> > Convert the OMAP GPIO Device Tree binding documentation to json-schema.
> > The GPIO hogs node names defined to end with a 'hog' suffix.
> >
> > All existing GPIO Hogs fixed to follow above naming convention
> > before changing the binding to avoid dtbs_check warnings.
>
> There is one note. The DT bindings change, without DTS changes, will
> cause dtbs_check warnings, so all these patches better to be merged through one tree.
So with the binding changes applied, I'm applying the dts changes
to omap-for-v5.14/dt thanks.
Regards,
Tony
prev parent reply other threads:[~2021-05-27 12:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 17:58 [PATCH v2 0/5] dt-bindings: gpio: omap: Convert to json-schema Grygorii Strashko
2021-05-25 17:58 ` [PATCH v2 1/5] ARM: dts: am335x: align GPIO hog names with dt-schema Grygorii Strashko
2021-05-25 17:58 ` [PATCH v2 2/5] ARM: dts: am437x: align gpio " Grygorii Strashko
2021-05-25 17:58 ` [PATCH v2 3/5] ARM: dts: omap3: " Grygorii Strashko
2021-05-25 17:58 ` [PATCH v2 4/5] ARM: dts: omap5-board-common: " Grygorii Strashko
2021-05-25 17:58 ` [PATCH v2 5/5] dt-bindings: gpio: omap: Convert to json-schema Grygorii Strashko
2021-05-26 11:28 ` Bartosz Golaszewski
2021-05-26 10:06 ` [PATCH v2 0/5] " Grygorii Strashko
2021-05-27 12:01 ` 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=YK+KEYncDc6pCb1X@atomide.com \
--to=tony@atomide.com \
--cc=a-govindraju@ti.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).