From: Colin Foster <colin.foster@in-advantage.com>
To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-phy@lists.infradead.org, linux-mips@vger.kernel.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
UNGLinuxDriver@microchip.com,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: [PATCH v2 0/1] Convert phy-ocelot-serdes documentation to YAML
Date: Sun, 11 Sep 2022 09:37:14 -0700 [thread overview]
Message-ID: <20220911163715.4036144-1-colin.foster@in-advantage.com> (raw)
Work is currently being done to add the phy-ocelot-serdes driver to a
non-syscon configuration. Doing so will require updates to the
documentation.
I can certainly wait until that change set to submit this, but I feel
sooner is better than later for Documentation format updates. Also,
those updates likely won't be ready before this next merge window.
The only liberty I took was adding Alexandre and UNGLinuxDriver as the
maintainers, otherwise the content should be the same.
v1 -> v2:
* Implemented changes from Krzysztof - see patch for details
Colin Foster (1):
dt-bindings: phy: ocelot-serdes: convert to YAML
.../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
--
2.25.1
next reply other threads:[~2022-09-11 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 16:37 Colin Foster [this message]
2022-09-11 16:37 ` [PATCH v2 1/1] dt-bindings: phy: ocelot-serdes: convert to YAML Colin Foster
2022-09-13 15:23 ` Rob Herring
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=20220911163715.4036144-1-colin.foster@in-advantage.com \
--to=colin.foster@in-advantage.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.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;
as well as URLs for NNTP newsgroup(s).