From: Boris Brezillon <boris.brezillon@collabora.com>
To: <Hari.PrasathGE@microchip.com>
Cc: <Manikandan.M@microchip.com>, <linux-kernel@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>, <Dharma.B@microchip.com>,
<sam@ravnborg.org>, <bbrezillon@kernel.org>,
<Nicolas.Ferre@microchip.com>
Subject: Re: [PATCH] MAINTAINERS: update Microchip's Atmel-HLCDC driver maintainers
Date: Thu, 20 Mar 2025 08:48:54 +0100 [thread overview]
Message-ID: <20250320084854.49d61c2a@collabora.com> (raw)
In-Reply-To: <662be697-acdb-42c2-8078-6baeb985a4ba@microchip.com>
On Mon, 17 Mar 2025 08:30:51 +0000
<Hari.PrasathGE@microchip.com> wrote:
> Hello,
>
> On 6/20/24 7:43 PM, Boris Brezillon wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >
> > On Thu, 20 Jun 2024 15:28:56 +0530
> > Manikandan Muralidharan <manikandan.m@microchip.com> wrote:
> >
> >> Drop Sam Ravnborg and Boris Brezillon as they are no longer interested in
> >> maintaining the drivers. Add myself and Dharma Balasubiramani as the
> >> Maintainer and co-maintainer for Microchip's Atmel-HLCDC driver.
> >> Thanks for their work.
> >>
> >> Signed-off-by: Manikandan Muralidharan <manikandan.m@microchip.com>
> >
> > Acked-by: Boris Brezillon <boris.brezillon@collabora.com>
> >
>
> Looks like this patch is still not applied. May I know if there is
> anything do be done from our side ?
Uh, sorry about that, I thought it had been applied by Sam. I just
queued the patch to drm-misc-next. Sorry again for the delay.
Regards,
Boris
next prev parent reply other threads:[~2025-03-20 7:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 9:58 [PATCH] MAINTAINERS: update Microchip's Atmel-HLCDC driver maintainers Manikandan Muralidharan
2024-06-20 12:57 ` Nicolas Ferre
2024-06-20 14:13 ` Boris Brezillon
2025-03-17 8:30 ` Hari.PrasathGE
2025-03-20 7:48 ` Boris Brezillon [this message]
2024-06-20 17:02 ` Sam Ravnborg
2024-09-25 10:22 ` Hari.PrasathGE
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=20250320084854.49d61c2a@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=Dharma.B@microchip.com \
--cc=Hari.PrasathGE@microchip.com \
--cc=Manikandan.M@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=bbrezillon@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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