From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Sowjanya Komatineni <skomatineni@nvidia.com>
Cc: linux-media@vger.kernel.org, linux-tegra@vger.kernel.org,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Joe Perches <joe@perches.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH] MAINTAINERS: correct path in TEGRA VIDEO DRIVER
Date: Mon, 11 May 2020 21:28:44 +0200 [thread overview]
Message-ID: <20200511192844.11044-1-lukas.bulwahn@gmail.com> (raw)
Commit 423d10a99b30 ("media: tegra: Add Tegra210 Video input driver") added
the driver to drivers/staging/media/tegra-video/, but commit 2c6b617f2cca
("MAINTAINERS: Add Tegra Video driver section") added a file entry
referring to drivers/staging/media/tegra/.
Hence, ./scripts/get_maintainer.pl --self-test=patterns complains:
warning: no file matches F: drivers/staging/media/tegra/
Adjust the file entry in TEGRA VIDEO DRIVER to the correct path.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
Sowjanya, please ack this minor patch.
applies cleanly on next-20200511
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 0abba1aff1ae..dd310f1c3bb7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -16679,7 +16679,7 @@ L: linux-media@vger.kernel.org
L: linux-tegra@vger.kernel.org
S: Maintained
F: Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.txt
-F: drivers/staging/media/tegra/
+F: drivers/staging/media/tegra-video/
TEGRA XUSB PADCTL DRIVER
M: JC Kuo <jckuo@nvidia.com>
--
2.17.1
next reply other threads:[~2020-05-11 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 19:28 Lukas Bulwahn [this message]
2020-05-11 19:44 ` [PATCH] MAINTAINERS: correct path in TEGRA VIDEO DRIVER Sowjanya Komatineni
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=20200511192844.11044-1-lukas.bulwahn@gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=joe@perches.com \
--cc=jonathanh@nvidia.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=skomatineni@nvidia.com \
--cc=thierry.reding@gmail.com \
/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