mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-media@vger.kernel.org, linux-tegra@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	linux-staging@lists.linux.dev, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: rectify entry for MEDIA DRIVERS FOR NVIDIA TEGRA - VDE
Date: Tue, 8 Mar 2022 03:17:35 +0300	[thread overview]
Message-ID: <e3c8078d-0e1a-6332-fbd5-6339561cd24d@gmail.com> (raw)
In-Reply-To: <20220307145935.13178-1-lukas.bulwahn@gmail.com>

07.03.2022 17:59, Lukas Bulwahn пишет:
> Commit ccc3016261ed ("media: dt: bindings: tegra-vde: Convert to schema")
> converts nvidia,tegra-vde.txt to nvidia,tegra-vde.yaml, but missed to
> adjust its reference in MAINTAINERS.
> 
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
> broken reference.
> 
> Repair this file reference in  MEDIA DRIVERS FOR NVIDIA TEGRA - VDE.
> 
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Dmitry, please ack.
> 
> Thierry, please pick this minor non-urgent clean-up patch.
> 
>  MAINTAINERS | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 05fd080b82f3..2b96a22cf5ea 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11964,7 +11964,7 @@ L:	linux-media@vger.kernel.org
>  L:	linux-tegra@vger.kernel.org
>  S:	Maintained
>  T:	git git://linuxtv.org/media_tree.git
> -F:	Documentation/devicetree/bindings/media/nvidia,tegra-vde.txt
> +F:	Documentation/devicetree/bindings/media/nvidia,tegra-vde.yaml
>  F:	drivers/staging/media/tegra-vde/
>  
>  MEDIA DRIVERS FOR RENESAS - CEU

This patch will have to go via the media tree. You'll may need to rebase
it on a recent linux-next soon because the driver path was changed
recently, otherwise maybe Mauro could resolve the merge conflict while
applying the patch.

Acked-by: Dmitry Osipenko <digetx@gmail.com>

      reply	other threads:[~2022-03-08  0:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 14:59 Lukas Bulwahn
2022-03-08  0:17 ` Dmitry Osipenko [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=e3c8078d-0e1a-6332-fbd5-6339561cd24d@gmail.com \
    --to=digetx@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=linux-tegra@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=mchehab@kernel.org \
    --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

all inboxes | Powered by JetHome®