From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Benoit Parrot <bparrot@ti.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH] MAINTAINERS: correct entry in TI VPE/CAL DRIVERS section
Date: Sat, 1 Feb 2020 16:17:14 +0100 [thread overview]
Message-ID: <20200201151714.26754-1-lukas.bulwahn@gmail.com> (raw)
perl scripts/parse-maintainers.pl complains:
Odd non-pattern line ' Documentation/devicetree/bindings/media/ti,cal.yaml
' for 'TI VPE/CAL DRIVERS' at scripts/parse-maintainers.pl line 147,
<$file> line 16742.
Commit 2099ef02c6c0 ("media: dt-bindings: media: cal: convert binding to
yaml") introduced this ill-formed line into MAINTAINERS.
Rectify it now.
Fixes: 2099ef02c6c0 ("media: dt-bindings: media: cal: convert binding to yaml")
Suggested-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
applies cleanly on current master and next-20200131
Benoit, please ack or pick this patch.
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 1f77fb8cdde3..e6890fa280d8 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -16738,7 +16738,7 @@ Q: http://patchwork.linuxtv.org/project/linux-media/list/
S: Maintained
F: drivers/media/platform/ti-vpe/
F: Documentation/devicetree/bindings/media/ti,vpe.yaml
- Documentation/devicetree/bindings/media/ti,cal.yaml
+F: Documentation/devicetree/bindings/media/ti,cal.yaml
TI WILINK WIRELESS DRIVERS
L: linux-wireless@vger.kernel.org
--
2.17.1
next reply other threads:[~2020-02-01 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 15:17 Lukas Bulwahn [this message]
2020-02-01 18:33 ` [PATCH] MAINTAINERS: correct entry in TI VPE/CAL DRIVERS section Andy Shevchenko
2020-02-01 19:20 ` Lukas Bulwahn
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=20200201151714.26754-1-lukas.bulwahn@gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=bparrot@ti.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@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).