From: Rob Herring <robh@kernel.org>
To: Colin Foster <colin.foster@in-advantage.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-phy@lists.infradead.org, linux-mips@vger.kernel.org,
Vinod Koul <vkoul@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Kishon Vijay Abraham I <kishon@ti.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
UNGLinuxDriver@microchip.com, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 1/1] dt-bindings: phy: ocelot-serdes: convert to YAML
Date: Tue, 13 Sep 2022 10:23:02 -0500 [thread overview]
Message-ID: <20220913152302.GA3762698-robh@kernel.org> (raw)
In-Reply-To: <20220911163715.4036144-2-colin.foster@in-advantage.com>
On Sun, 11 Sep 2022 09:37:15 -0700, Colin Foster wrote:
> Convert the phy-ocelot-serdes device tree binding to the new YAML format.
>
> Additionally, add the file to MAINTAINERS since the original file didn't
> exist.
>
> Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
> ---
>
> v1 -> v2:
> * new yaml file is now named mscc,vsc7514-serdes.yaml
> * examlpes != examples
> * remove "driver" name from the binding
> * remove ethernet port consumer from the example
> * add additionalProperties: false
> * remove unnecessary, obvious sentence in the description
>
> ---
> .../bindings/phy/mscc,vsc7514-serdes.yaml | 56 +++++++++++++++++++
> .../bindings/phy/phy-ocelot-serdes.txt | 43 --------------
> MAINTAINERS | 1 +
> 3 files changed, 57 insertions(+), 43 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/phy/mscc,vsc7514-serdes.yaml
> delete mode 100644 Documentation/devicetree/bindings/phy/phy-ocelot-serdes.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-09-13 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 16:37 [PATCH v2 0/1] Convert phy-ocelot-serdes documentation to YAML Colin Foster
2022-09-11 16:37 ` [PATCH v2 1/1] dt-bindings: phy: ocelot-serdes: convert " Colin Foster
2022-09-13 15:23 ` Rob Herring [this message]
2022-09-13 16:40 ` Vinod Koul
2022-09-13 16:44 ` Colin Foster
2022-09-13 16:46 ` Colin Foster
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=20220913152302.GA3762698-robh@kernel.org \
--to=robh@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=colin.foster@in-advantage.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@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