public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Steven Price <steven.price@arm.com>
Cc: "Adrián Larumbe" <adrian.larumbe@collabora.com>,
	linux-kernel@vger.kernel.org, "Rob Herring" <robh@kernel.org>,
	dri-devel@lists.freedesktop.org, kernel@collabora.com
Subject: Re: [PATCH v5 12/12] MAINTAINERS: Add Adrian Larumbe as Panfrost driver maintainer
Date: Thu, 9 Oct 2025 17:56:01 +0200	[thread overview]
Message-ID: <20251009175601.0eeb27c5@fedora> (raw)
In-Reply-To: <971fd0e3-474a-4685-ade2-f4563372f74d@arm.com>

On Thu, 9 Oct 2025 16:47:26 +0100
Steven Price <steven.price@arm.com> wrote:

> On 07/10/2025 16:01, Adrián Larumbe wrote:
> > Add Adrian Larumbe as Panfrost driver maintainer.
> > 
> > Signed-off-by: Adrián Larumbe <adrian.larumbe@collabora.com>  
> 
> Acked-by: Steven Price <steven.price@arm.com>
> 
> Welcome! And thank you for helping out.
> 
> > ---
> >  MAINTAINERS | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 5257d52679d6..cb68fdec3da4 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -2066,6 +2066,7 @@ F:	drivers/gpu/drm/arm/display/komeda/
> >  ARM MALI PANFROST DRM DRIVER
> >  M:	Boris Brezillon <boris.brezillon@collabora.com>
> >  M:	Rob Herring <robh@kernel.org>
> > +M:      Adrián Larumbe <adrian.larumbe@collabora.com>  
> 
> NIT: it looks like you've used spaces not a tab.
> 
> Also while we're here...
> 
> @RobH: Does it still make sense for you to be listed as a maintainer? I
> haven't seen you active on Panfrost for a while.
> 
> >  R:	Steven Price <steven.price@arm.com>  
> 
> And given that I've been doing a fair bit of the merging recently I'm
> wondering if I should upgrade myself to 'M'?

Oh, I didn't notice you were only flagged as a reviewer. +1 on turning
this R into an M.

  reply	other threads:[~2025-10-09 15:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07 15:01 [PATCH v5 00/12] Some Panfrost fixes and improvements Adrián Larumbe
2025-10-07 15:01 ` [PATCH v5 01/12] drm/panfrost: Replace DRM driver allocation method with newer one Adrián Larumbe
2025-10-07 15:01 ` [PATCH v5 02/12] drm/panfrost: Handle inexistent GPU during probe Adrián Larumbe
2025-10-07 15:01 ` [PATCH v5 03/12] drm/panfrost: Handle job HW submit errors Adrián Larumbe
2025-10-09 15:17   ` Steven Price
2025-10-07 15:01 ` [PATCH v5 04/12] drm/panfrost: Handle error when allocating AS number Adrián Larumbe
2025-10-09 15:17   ` Steven Price
2025-10-07 15:01 ` [PATCH v5 05/12] drm/panfrost: Check sgt to know whether pages are already mapped Adrián Larumbe
2025-10-07 16:20   ` Boris Brezillon
2025-10-07 15:01 ` [PATCH v5 06/12] drm/panfrost: Handle page mapping failure Adrián Larumbe
2025-10-07 16:24   ` Boris Brezillon
2025-10-07 15:01 ` [PATCH v5 07/12] drm/panfrost: Don't rework job IRQ enable mask in the enable path Adrián Larumbe
2025-10-09 15:33   ` Steven Price
2025-10-07 15:01 ` [PATCH v5 08/12] drm/panfrost: Make re-enabling job interrupts at device reset optional Adrián Larumbe
2025-10-09 15:35   ` Steven Price
2025-10-07 15:01 ` [PATCH v5 09/12] drm/panfrost: Add forward declaration and types header Adrián Larumbe
2025-10-09 15:36   ` Steven Price
2025-10-07 15:01 ` [PATCH v5 10/12] drm/panfrost: Remove unused device property Adrián Larumbe
2025-10-09 15:37   ` Steven Price
2025-10-07 15:01 ` [PATCH v5 11/12] drm/panfrost: Rename panfrost_job functions to reflect real role Adrián Larumbe
2025-10-09 15:43   ` Steven Price
2025-10-07 15:01 ` [PATCH v5 12/12] MAINTAINERS: Add Adrian Larumbe as Panfrost driver maintainer Adrián Larumbe
2025-10-09 15:26   ` Boris Brezillon
2025-10-09 15:47   ` Steven Price
2025-10-09 15:56     ` Boris Brezillon [this message]
2025-10-14 23:25     ` Adrián Larumbe

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=20251009175601.0eeb27c5@fedora \
    --to=boris.brezillon@collabora.com \
    --cc=adrian.larumbe@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=steven.price@arm.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