From: "Heiko Stübner" <heiko@sntech.de>
To: Detlev Casanova <detlev.casanova@collabora.com>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Lukas Bulwahn <lbulwahn@redhat.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: merge sections for ROCKCHIP VIDEO DECODER DRIVER
Date: Tue, 15 Jul 2025 09:16:55 +0200 [thread overview]
Message-ID: <3261271.ElGaqSPkdT@diego> (raw)
In-Reply-To: <20250715063134.100733-1-lukas.bulwahn@redhat.com>
Am Dienstag, 15. Juli 2025, 08:31:34 Mitteleuropäische Sommerzeit schrieb Lukas Bulwahn:
> From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
>
> Commit d968e50b5c26 ("media: rkvdec: Unstage the driver") moves the driver
> from staging/media/ to media/platform/rockchip/ and adds a new section
> ROCKCHIP RKVDEC VIDEO DECODER DRIVER in MAINTAINERS. It seems that it was
> overlooked that the section ROCKCHIP VIDEO DECODER DRIVER in MAINTAINERS
> already existed, referring to the same files before the driver was moved
> as the new section refers to after the driver was moved.
>
> So, merge the information from the two sections for ROCKCHIP (RKVDEC) VIDEO
> DECODER DRIVER into one. This essentially results in adding the maintainer
> of the previously existing section in the new section and then removing
> that previously existing section.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
> ---
> MAINTAINERS | 9 +--------
> 1 file changed, 1 insertion(+), 8 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 5efcdb5537f5..d044e4f71ae5 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -21673,6 +21673,7 @@ F: drivers/media/platform/rockchip/rga/
>
> ROCKCHIP RKVDEC VIDEO DECODER DRIVER
> M: Detlev Casanova <detlev.casanova@collabora.com>
> +M: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> L: linux-media@vger.kernel.org
> L: linux-rockchip@lists.infradead.org
> S: Maintained
> @@ -21693,14 +21694,6 @@ S: Maintained
> F: Documentation/devicetree/bindings/sound/rockchip,rk3576-sai.yaml
> F: sound/soc/rockchip/rockchip_sai.*
>
> -ROCKCHIP VIDEO DECODER DRIVER
> -M: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> -L: linux-media@vger.kernel.org
> -L: linux-rockchip@lists.infradead.org
> -S: Maintained
> -F: Documentation/devicetree/bindings/media/rockchip,vdec.yaml
> -F: drivers/staging/media/rkvdec/
> -
> ROCKER DRIVER
> M: Jiri Pirko <jiri@resnulli.us>
> L: netdev@vger.kernel.org
>
prev parent reply other threads:[~2025-07-15 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 6:31 [PATCH] MAINTAINERS: merge sections for ROCKCHIP VIDEO DECODER DRIVER Lukas Bulwahn
2025-07-15 7:16 ` Heiko Stübner [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=3261271.ElGaqSPkdT@diego \
--to=heiko@sntech.de \
--cc=detlev.casanova@collabora.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=hverkuil@xs4all.nl \
--cc=kernel-janitors@vger.kernel.org \
--cc=lbulwahn@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lukas.bulwahn@redhat.com \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.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;
as well as URLs for NNTP newsgroup(s).