From: "Rob Herring (Arm)" <robh@kernel.org>
To: "Maíra Canal" <mcanal@igalia.com>
Cc: kernel-dev@igalia.com, Nicolas Saenz Julienne <nsaenz@kernel.org>,
Iago Toral <itoral@igalia.com>,
dri-devel@lists.freedesktop.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, Melissa Wen <mwen@igalia.com>,
Jose Maria Casanova Crespo <jmcasanova@igalia.com>
Subject: Re: [PATCH 6/6] dt-bindings: gpu: Add V3D driver maintainer as DT maintainer
Date: Mon, 3 Mar 2025 08:05:51 -0600 [thread overview]
Message-ID: <174101075097.1758007.4807852577942863948.robh@kernel.org> (raw)
In-Reply-To: <20250226-v3d-gpu-reset-fixes-v1-6-83a969fdd9c1@igalia.com>
On Wed, 26 Feb 2025 16:59:04 -0300, Maíra Canal wrote:
> As established in commit 89d04995f76c ("MAINTAINERS: Drop Emma Anholt
> from all M lines."), Emma is no longer active in the Linux kernel and
> dropped the V3D maintainership. Therefore, remove Emma as one of the DT
> maintainers and add the current V3D driver maintainer.
>
> Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
> Cc: Conor Dooley <conor+dt@kernel.org>
> Cc: Nicolas Saenz Julienne <nsaenz@kernel.org>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Maíra Canal <mcanal@igalia.com>
> ---
> Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-03-03 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 19:58 [PATCH 0/6] drm/v3d: Fix GPU reset issues on the Raspberry Pi 5 Maíra Canal
2025-02-26 19:59 ` [PATCH 4/6] dt-bindings: gpu: v3d: Add SMS to the registers' list Maíra Canal
2025-02-28 19:07 ` Conor Dooley
2025-02-26 19:59 ` [PATCH 6/6] dt-bindings: gpu: Add V3D driver maintainer as DT maintainer Maíra Canal
2025-03-03 14:05 ` Rob Herring (Arm) [this message]
2025-02-27 7:55 ` [PATCH 0/6] drm/v3d: Fix GPU reset issues on the Raspberry Pi 5 Iago Toral
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=174101075097.1758007.4807852577942863948.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=itoral@igalia.com \
--cc=jmcasanova@igalia.com \
--cc=kernel-dev@igalia.com \
--cc=krzk+dt@kernel.org \
--cc=mcanal@igalia.com \
--cc=mwen@igalia.com \
--cc=nsaenz@kernel.org \
/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