From: Andy Yan <andy.yan@rock-chips.com>
To: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
Heiko Stuebner <heiko@sntech.de>,
Sandy Huang <hjc@rock-chips.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH RFC] MAINTAINERS: Track dw-hdmi-qp under Rockchip DRM drivers
Date: Wed, 6 May 2026 10:02:33 +0800 [thread overview]
Message-ID: <f91f1ebe-c41e-42ae-a860-5e4c99c34784@rock-chips.com> (raw)
In-Reply-To: <20260506-maintainers-rk-drm-upd-v1-1-f67537b4bb29@collabora.com>
Hello,
On 5/6/26 06:31, Cristian Ciocaltea wrote:
> The DW HDMI QP TX library was developed for and is currently only used
> by Rockchip platforms. Add it to the Rockchip DRM drivers section to
> ensure all relevant parties are kept in the loop on any changes.
>
> As its file paths fall outside the generic wildcard patterns defined in
> the ARM/Rockchip SoC support section, also add the
> linux-rockchip@lists.infradead.org mailing list to avoid any
> notification gaps.
>
> Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
> ---
> MAINTAINERS | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 0dfad67f66c0..cb3c8e5fcb21 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8754,11 +8754,14 @@ M: Sandy Huang <hjc@rock-chips.com>
> M: Heiko Stübner <heiko@sntech.de>
> M: Andy Yan <andy.yan@rock-chips.com>
> L: dri-devel@lists.freedesktop.org
> +L: linux-rockchip@lists.infradead.org
> S: Maintained
> T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
> F: Documentation/devicetree/bindings/display/rockchip/
> +F: drivers/gpu/drm/bridge/synopsys/dw-hdmi-qp.*
> F: drivers/gpu/drm/ci/xfails/rockchip*
> F: drivers/gpu/drm/rockchip/
> +F: include/drm/bridge/dw_hdmi_qp.h
Acked-by: Andy Yan <andy.yan@rock-chips.com>
>
> DRM DRIVERS FOR STI
> M: Alain Volmat <alain.volmat@foss.st.com>
>
> ---
> base-commit: 4cd074ae20bbcc293bbbce9163abe99d68ae6ae0
> change-id: 20260506-maintainers-rk-drm-upd-c463f6b04769
>
>
prev parent reply other threads:[~2026-05-06 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 22:31 [PATCH RFC] MAINTAINERS: Track dw-hdmi-qp under Rockchip DRM drivers Cristian Ciocaltea
2026-05-06 2:02 ` Andy Yan [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=f91f1ebe-c41e-42ae-a860-5e4c99c34784@rock-chips.com \
--to=andy.yan@rock-chips.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=cristian.ciocaltea@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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