From: Neil Armstrong <narmstrong@baylibre.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: linux-amlogic@lists.infradead.org,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
linux-spi <linux-spi@vger.kernel.org>,
LINUX-WATCHDOG <linux-watchdog@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
devicetree@vger.kernel.org, Jassi Brar <jassisinghbrar@gmail.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [RFCv2 0/9] dt-bindings: first tentative of conversion to yaml format
Date: Tue, 6 Aug 2019 09:42:19 +0200 [thread overview]
Message-ID: <4e87b12f-ef92-49d8-1e1d-9bc5ba5c3c8d@baylibre.com> (raw)
In-Reply-To: <CAL_JsqJzwtSXX0nrS7RBP8u-e=16SiWOBjLrvy8Amc08PfpXag@mail.gmail.com>
Hi Rob,
On 05/08/2019 23:51, Rob Herring wrote:
> On Mon, Aug 5, 2019 at 6:03 AM Neil Armstrong <narmstrong@baylibre.com> wrote:
>>
>> This is a first tentative to convert some of the simplest Amlogic
>> dt-bindings to the yaml format.
>>
>> All have been tested using :
>> $ make ARCH=arm64 dtbs_check
>>
>> Issues with the amlogic arm64 DTs has already been identified thanks
>> to the validation scripts. The DT fixes will be pushed once these yaml
>> bindings are acked.
>>
>> Changes since rfc v1:
>> - Fixed bindings according to Rob's comments
>> - Added commit log
>> - renamed yaml files using amlogic prefix
>>
>> Neil Armstrong (9):
>> dt-bindings: mailbox: meson-mhu: convert to yaml
>> dt-bindings: rng: amlogic,meson-rng: convert to yaml
>> dt-bindings: spi: meson: convert to yaml
>> dt-bindings: reset: amlogic,meson-reset: convert to yaml
>> dt-bindings: arm: amlogic: amlogic,meson-gx-ao-secure: convert to yaml
>> dt-bindings: phy: meson-g12a-usb2-phy: convert to yaml
>> dt-bindings: phy: meson-g12a-usb3-pcie-phy: convert to yaml
>> dt-bindings: serial: meson-uart: convert to yaml
>> dt-bindings: watchdog: meson-gxbb-wdt: convert to yaml
>
> For the series,
>
> Reviewed-by: Rob Herring <robh@kernel.org>
>
> What's your merge plan? Do you want me to take the whole series?
I planned to split them for each subsystem, but it may be much simpler
if you take the whole serie.
Neil
>
> Rob
>
prev parent reply other threads:[~2019-08-06 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 12:03 [RFCv2 0/9] dt-bindings: first tentative of conversion to yaml format Neil Armstrong
2019-08-05 12:03 ` [RFCv2 9/9] dt-bindings: watchdog: meson-gxbb-wdt: convert to yaml Neil Armstrong
2019-08-07 17:59 ` Guenter Roeck
2019-08-05 21:51 ` [RFCv2 0/9] dt-bindings: first tentative of conversion to yaml format Rob Herring
2019-08-06 7:42 ` Neil Armstrong [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=4e87b12f-ef92-49d8-1e1d-9bc5ba5c3c8d@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=kishon@ti.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@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).