From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
Konstantin Porotchkin <kostap@marvell.com>,
Rob Herring <robh@kernel.org>, Vinod Koul <vkoul@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 09/12] MAINTAINERS: update marvell,armada-3700-utmi-phy.yaml reference
Date: Wed, 2 Jun 2021 17:43:15 +0200 [thread overview]
Message-ID: <9342a88ed44726a1cc405470c834d746d4d0524c.1622648507.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1622648507.git.mchehab+huawei@kernel.org>
Changeset 6569d8386388 ("dt-bindings: phy: convert phy-mvebu-utmi to YAML schema")
renamed: Documentation/devicetree/bindings/phy/phy-mvebu-utmi.txt
to: Documentation/devicetree/bindings/phy/marvell,armada-3700-utmi-phy.yaml.
Update its cross-reference accordingly.
Fixes: 6569d8386388 ("dt-bindings: phy: convert phy-mvebu-utmi to YAML schema")
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8b423b7246a3..644572ab4b2d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10960,7 +10960,7 @@ MARVELL ARMADA 3700 PHY DRIVERS
M: Miquel Raynal <miquel.raynal@bootlin.com>
S: Maintained
F: Documentation/devicetree/bindings/phy/phy-mvebu-comphy.txt
-F: Documentation/devicetree/bindings/phy/phy-mvebu-utmi.txt
+F: Documentation/devicetree/bindings/phy/marvell,armada-3700-utmi-phy.yaml
F: drivers/phy/marvell/phy-mvebu-a3700-comphy.c
F: drivers/phy/marvell/phy-mvebu-a3700-utmi.c
--
2.31.1
next prev parent reply other threads:[~2021-06-02 15:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 15:43 [PATCH 00/12] Fix broken docs references at next-20210602 Mauro Carvalho Chehab
2021-06-02 15:43 ` [PATCH 01/12] dt-bindings: power: supply: cpcap-battery: update cpcap-battery.yaml reference Mauro Carvalho Chehab
2021-06-03 1:54 ` Rob Herring
2021-06-02 15:43 ` [PATCH 02/12] dt-bindings: power: supply: cpcap-charger: update cpcap-charger.yaml reference Mauro Carvalho Chehab
2021-06-03 1:54 ` Rob Herring
2021-06-02 15:43 ` [PATCH 03/12] dt-bindings: soc: ti: update sci-pm-domain.yaml references Mauro Carvalho Chehab
2021-06-02 21:03 ` Rob Herring
2021-06-03 20:08 ` Wolfram Sang
2021-06-02 15:43 ` [PATCH 04/12] dt-bindings: clock: update ti,sci-clk.yaml references Mauro Carvalho Chehab
2021-06-02 21:04 ` Rob Herring
2021-06-03 20:09 ` Wolfram Sang
2021-06-02 15:43 ` [PATCH 05/12] dt-bindings: reset: update ti,sci-reset.yaml references Mauro Carvalho Chehab
2021-06-02 21:04 ` Rob Herring
2021-06-02 15:43 ` [PATCH 06/12] dt-bindings: iio: io-channel-mux.yaml: fix a typo Mauro Carvalho Chehab
2021-06-02 21:04 ` Rob Herring
2021-06-02 15:43 ` [PATCH 07/12] docs: accounting: update delay-accounting.rst reference Mauro Carvalho Chehab
2021-06-02 16:38 ` Peter Zijlstra
2021-06-02 18:01 ` Mauro Carvalho Chehab
2021-06-02 18:29 ` Peter Zijlstra
2021-06-02 18:36 ` Jonathan Corbet
2021-06-02 20:19 ` Mauro Carvalho Chehab
2021-06-03 7:20 ` Peter Zijlstra
2021-06-03 7:56 ` Mauro Carvalho Chehab
2021-07-04 13:52 ` Federico Vaga
2021-06-03 11:35 ` Mauro Carvalho Chehab
2021-06-02 15:43 ` [PATCH 08/12] MAINTAINERS: update faraday,ftrtc010.yaml reference Mauro Carvalho Chehab
2021-06-06 22:50 ` Linus Walleij
2021-06-07 8:14 ` Alexandre Belloni
2021-06-02 15:43 ` Mauro Carvalho Chehab [this message]
2021-06-03 6:11 ` [PATCH 09/12] MAINTAINERS: update marvell,armada-3700-utmi-phy.yaml reference Vinod Koul
2021-06-02 15:43 ` [PATCH 10/12] MAINTAINERS: update ti,omap-gpio.yaml reference Mauro Carvalho Chehab
2021-06-07 14:15 ` Bartosz Golaszewski
2021-06-02 15:43 ` [PATCH 11/12] MAINTAINERS: update ti,sci.yaml reference Mauro Carvalho Chehab
2021-06-02 15:43 ` [PATCH 12/12] MAINTAINERS: update nxp,imx8-jpeg.yaml reference Mauro Carvalho Chehab
2021-06-03 8:18 ` [EXT] " Mirela Rabulea
2021-06-03 20:00 ` [PATCH 00/12] Fix broken docs references at next-20210602 Rob Herring
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=9342a88ed44726a1cc405470c834d746d4d0524c.1622648507.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=kostap@marvell.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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).