From: Krzysztof Kozlowski <krzk@kernel.org>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>, Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
LUU HOAI <hoai.luu.ub@renesas.com>,
Jagan Teki <jagan@amarulasolutions.com>,
Sam Ravnborg <sam@ravnborg.org>,
Biju Das <biju.das.jz@bp.renesas.com>
Cc: dri-devel@lists.freedesktop.org,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-clk@vger.kernel.org, stable@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v5 0/7] drm: Add DSI/DP support for Renesas r8a779h0 V4M and grey-hawk board
Date: Tue, 28 Jan 2025 11:09:40 +0100 [thread overview]
Message-ID: <1e9f7f94-3d0c-4258-b9de-746d0b22ec06@kernel.org> (raw)
In-Reply-To: <aa858619-56f6-4d3a-b27d-f38cbfa57d98@ideasonboard.com>
On 17/12/2024 14:33, Tomi Valkeinen wrote:
> Hi all,
>
> On 17/12/2024 07:31, Tomi Valkeinen wrote:
>> Add everything needed to support the DSI output on Renesas r8a779h0
>> (V4M) SoC, and the DP output (via sn65dsi86 DSI to DP bridge) on the
>> Renesas grey-hawk board.
>>
>> Overall the DSI and the board design is almost identical to Renesas
>> r8a779g0 and white-hawk board.
>>
>> Note: the v4 no longer has the dts and the clk patches, as those have
>> been merged to renesas-devel.
>>
>
> I have pushed this to drm-misc-next. Thank you all for the reviews!
I am confused how this is supposed to work. You merged your own patches
for Renesas DRM, even not being the Renesas DRM maintainer, while my
much earlier patchset was "only" reviewed by Renesas DRM maintainers but
not picked up by them.
So maybe you are the Renesas DRM maintainer? But get_maintainers.pl is
silent on that, so I don't Cc you.
Can you guys clarify that so maintainers file reflect reality?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-28 10:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 5:31 [PATCH v5 0/7] drm: Add DSI/DP support for Renesas r8a779h0 V4M and grey-hawk board Tomi Valkeinen
2024-12-17 5:31 ` [PATCH v5 1/7] drm/rcar-du: dsi: Fix PHY lock bit check Tomi Valkeinen
2024-12-17 5:31 ` [PATCH v5 2/7] drm/rcar-du: Write DPTSR only if the second source exists Tomi Valkeinen
2024-12-17 5:31 ` [PATCH v5 3/7] dt-bindings: display: renesas,du: Add missing constraints Tomi Valkeinen
2024-12-17 6:25 ` Krzysztof Kozlowski
2025-01-28 9:42 ` Krzysztof Kozlowski
2025-01-28 10:38 ` Tomi Valkeinen
2024-12-17 8:14 ` [PATCH v5 3/7] dt-bindings: display: renesas, du: " Geert Uytterhoeven
2024-12-17 9:59 ` [PATCH v5 3/7] dt-bindings: display: renesas,du: " Tomi Valkeinen
2024-12-17 11:42 ` Laurent Pinchart
2024-12-17 11:44 ` Laurent Pinchart
2024-12-17 5:31 ` [PATCH v5 4/7] dt-bindings: display: renesas,du: Add r8a779h0 Tomi Valkeinen
2024-12-17 6:28 ` Krzysztof Kozlowski
2024-12-17 6:33 ` Tomi Valkeinen
2024-12-17 5:31 ` [PATCH v5 5/7] dt-bindings: display: bridge: renesas,dsi-csi2-tx: " Tomi Valkeinen
2024-12-17 5:31 ` [PATCH v5 6/7] drm/rcar-du: dsi: Add r8a779h0 support Tomi Valkeinen
2024-12-17 5:31 ` [PATCH v5 7/7] drm/rcar-du: Add support for r8a779h0 Tomi Valkeinen
2024-12-17 13:33 ` [PATCH v5 0/7] drm: Add DSI/DP support for Renesas r8a779h0 V4M and grey-hawk board Tomi Valkeinen
2025-01-28 10:09 ` Krzysztof Kozlowski [this message]
2025-01-28 10:26 ` Tomi Valkeinen
2025-01-28 10:28 ` Krzysztof Kozlowski
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=1e9f7f94-3d0c-4258-b9de-746d0b22ec06@kernel.org \
--to=krzk@kernel.org \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert+renesas@glider.be \
--cc=hoai.luu.ub@renesas.com \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=magnus.damm@gmail.com \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=sam@ravnborg.org \
--cc=sboyd@kernel.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=tomi.valkeinen@ideasonboard.com \
--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;
as well as URLs for NNTP newsgroup(s).