linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
	Andre Przywara <andre.przywara@arm.com>,
	Rob Herring <robh@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 14/23] MAINTAINERS: update arm,hdlcd.yaml reference
Date: Mon,  6 Jun 2022 16:25:36 +0100	[thread overview]
Message-ID: <714c3b6e10736d51268b9d71b97829a224b3bae1.1654529011.git.mchehab@kernel.org> (raw)
In-Reply-To: <cover.1654529011.git.mchehab@kernel.org>

Changeset 36fd2a65bcaf ("dt-bindings: display: convert Arm HDLCD to DT schema")
renamed: Documentation/devicetree/bindings/display/arm,hdlcd.txt
to: Documentation/devicetree/bindings/display/arm,hdlcd.yaml.

Update its cross-reference accordingly.

Fixes: 36fd2a65bcaf ("dt-bindings: display: convert Arm HDLCD to DT schema")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH 00/23] at: https://lore.kernel.org/all/cover.1654529011.git.mchehab@kernel.org/

 MAINTAINERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index a6d3bd9d2a8d..c20bd168d209 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1507,7 +1507,7 @@ F:	drivers/clocksource/arm_arch_timer.c
 ARM HDLCD DRM DRIVER
 M:	Liviu Dudau <liviu.dudau@arm.com>
 S:	Supported
-F:	Documentation/devicetree/bindings/display/arm,hdlcd.txt
+F:	Documentation/devicetree/bindings/display/arm,hdlcd.yaml
 F:	drivers/gpu/drm/arm/hdlcd_*
 
 ARM INTEGRATOR, VERSATILE AND REALVIEW SUPPORT
-- 
2.36.1


  parent reply	other threads:[~2022-06-06 15:26 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 15:25 [PATCH 00/23] Update Documentation/ cross-references Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 01/23] dt-bindings: mfd: bd9571mwv: update rohm,bd9571mwv.yaml reference Mauro Carvalho Chehab
2022-06-07 19:25   ` Geert Uytterhoeven
2022-06-06 15:25 ` [PATCH 02/23] dt-bindings: interrupt-controller: update brcm,l2-intc.yaml reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 03/23] dt-bindings: arm: update vexpress-config.yaml references Mauro Carvalho Chehab
2022-06-06 15:44   ` Guenter Roeck
2022-06-06 15:25 ` [PATCH 04/23] dt-bindings: reset: update st,stih407-powerdown.yaml references Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 05/23] dt-bindings: mfd: rk808: update rockchip,rk808.yaml reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 06/23] dt-bindings: mmc: exynos-dw-mshc: update samsung,pinctrl.yaml reference Mauro Carvalho Chehab
2022-06-06 15:41   ` Krzysztof Kozlowski
2022-06-07 12:15     ` Krzysztof Kozlowski
2022-06-06 15:25 ` [PATCH 07/23] docs: netdev: update maintainer-netdev.rst reference Mauro Carvalho Chehab
2022-06-06 16:22   ` Jakub Kicinski
2022-06-06 15:25 ` [PATCH 08/23] docs: filesystems: update netfs-api.rst reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 09/23] Documentation: update watch_queue.rst references Mauro Carvalho Chehab
2022-06-06 15:56   ` Randy Dunlap
2022-06-06 15:25 ` [PATCH 10/23] Documentation: KVM: update s390-pv.rst reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 11/23] Documentation: KVM: update amd-memory-encryption.rst references Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 12/23] Documentation: KVM: update msr.rst reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 13/23] Documentation: KVM: update s390-diag.rst reference Mauro Carvalho Chehab
2022-06-06 15:25 ` Mauro Carvalho Chehab [this message]
2022-06-06 15:34   ` [PATCH 14/23] MAINTAINERS: update arm,hdlcd.yaml reference Andre Przywara
2022-06-06 17:13     ` Rob Herring
2022-06-06 15:25 ` [PATCH 15/23] MAINTAINERS: update arm,komeda.yaml reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 16/23] MAINTAINERS: update arm,malidp.yaml reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 17/23] MAINTAINERS: update cortina,gemini-ethernet.yaml reference Mauro Carvalho Chehab
2022-06-07 22:42   ` Linus Walleij
2022-06-06 15:25 ` [PATCH 18/23] MAINTAINERS: update dongwoon,dw9807-vcm.yaml reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 19/23] MAINTAINERS: update maxim,max77693.yaml reference Mauro Carvalho Chehab
2022-06-06 15:37   ` Krzysztof Kozlowski
2022-06-06 15:25 ` [PATCH 20/23] MAINTAINERS: update snps,axs10x-reset.yaml reference Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 21/23] objtool: update objtool.txt references Mauro Carvalho Chehab
2022-06-06 15:25 ` [PATCH 22/23] ASoC: wm8731: update wlf,wm8731.yaml reference Mauro Carvalho Chehab
2022-06-06 19:01   ` Rob Herring
2022-06-13  9:47   ` Charles Keepax
2022-06-06 15:25 ` [PATCH 23/23] arch: m68k: q40: README: drop references to IDE driver Mauro Carvalho Chehab
2022-06-06 16:07   ` Randy Dunlap
2022-06-07  8:07   ` Geert Uytterhoeven
2022-06-06 17:17 ` [PATCH 00/23] Update Documentation/ cross-references Rob Herring
2022-06-07 14:11 ` (subset) " Mark Brown

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=714c3b6e10736d51268b9d71b97829a224b3bae1.1654529011.git.mchehab@kernel.org \
    --to=mchehab@kernel.org \
    --cc=andre.przywara@arm.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=robh@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).