Linux Media Controller development
 help / color / mirror / Atom feed
From: Sowjanya Komatineni <skomatineni@nvidia.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@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>
Subject: Re: [PATCH] MAINTAINERS: correct path in TEGRA VIDEO DRIVER
Date: Mon, 11 May 2020 12:44:11 -0700	[thread overview]
Message-ID: <00ec3aa4-07c5-49ed-df89-de3f7f8b8cd8@nvidia.com> (raw)
In-Reply-To: <20200511192844.11044-1-lukas.bulwahn@gmail.com>


On 5/11/20 12:28 PM, Lukas Bulwahn wrote:
> 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(-)
Acked-by: Sowjanya Komatineni <skomatineni@nvidia.com>

      reply	other threads:[~2020-05-11 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 19:28 [PATCH] MAINTAINERS: correct path in TEGRA VIDEO DRIVER Lukas Bulwahn
2020-05-11 19:44 ` Sowjanya Komatineni [this message]

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=00ec3aa4-07c5-49ed-df89-de3f7f8b8cd8@nvidia.com \
    --to=skomatineni@nvidia.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=lukas.bulwahn@gmail.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