From: Jianmin Lv <lvjianmin@loongson.cn>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: 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>,
Qianhai Wu <wuqianhai@loongson.cn>,
Mingcong Bai <jeffbai@aosc.io>, Xi Ruoyao <xry111@xry111.site>,
Xuefeng Li <lixuefeng@loongson.cn>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] MAINTAINERS: Update GPU driver maintainer information
Date: Thu, 19 Mar 2026 09:58:32 +0800 [thread overview]
Message-ID: <16f3d7c5-d87c-e415-5efe-975d417e14d1@loongson.cn> (raw)
In-Reply-To: <CAAhV-H5hcnGAE2xYU-eKuWWCyJkW5mfn_wyS49_MTpz5K+8zEw@mail.gmail.com>
On 2026/3/18 下午5:42, Huacai Chen wrote:
> Thanks for the invitation and will try my best to help, too.
>
> BTW, please spend some time to review this patch:
> https://lore.kernel.org/dri-devel/c6013f25-fce0-41ba-a275-96188a6647c1@suse.de/T/#t
>
Ok, I'll look into it as soon as possible.
thanks.
> On Wed, Mar 18, 2026 at 5:31 PM Jianmin Lv <lvjianmin@loongson.cn> wrote:
>>
>> I and Qianhai are GPU R&D engineers at Loongson, specializing
>> in kernel driver development. We understand that the current
>> Loongson GPU driver lacks dedicated maintenance resources
>> because of some reasons.
>>
>> As Loongson GPU driver developers, we have both the capability
>> and the responsibility to continuously maintain the Loongson
>> GPU driver, ensuring minimal impact on its users. After internal
>> discussions, our team has decided to recommend me and Qianhai
>> to take over the maintenance responsibilities, and recommend
>> Huacai, Mingcong and Ruoyao to help to review.
>>
>> And We'll continue to maintain it for current supported chips
>> and drive future updates according to chip support plan.
>>
>> Signed-off-by: Jianmin Lv <lvjianmin@loongson.cn>
> Acked-by: Huacai Chen <chenhuacai@kernel.org>
>
>
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 96ea84948d76..4232039b7282 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -8626,8 +8626,13 @@ F: drivers/gpu/drm/lima/
>> F: include/uapi/drm/lima_drm.h
>>
>> DRM DRIVERS FOR LOONGSON
>> +M: Jianmin Lv <lvjianmin@loongson.cn>
>> +M: Qianhai Wu <wuqianhai@loongson.cn>
>> +R: Huacai Chen <chenhuacai@kernel.org>
>> +R: Mingcong Bai <jeffbai@aosc.io>
>> +R: Xi Ruoyao <xry111@xry111.site>
>> L: dri-devel@lists.freedesktop.org
>> -S: Orphan
>> +S: Maintained
>> T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
>> F: drivers/gpu/drm/loongson/
>>
>> --
>> 2.20.1
>>
next prev parent reply other threads:[~2026-03-19 2:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 9:23 Jianmin Lv
2026-03-18 9:35 ` Mingcong Bai
2026-03-18 9:42 ` Huacai Chen
2026-03-19 1:58 ` Jianmin Lv [this message]
2026-03-19 2:05 ` wuqianhai
2026-03-19 7:54 ` Thomas Zimmermann
2026-03-19 8:51 ` Icenowy Zheng
2026-03-19 13:08 ` Jianmin Lv
2026-03-19 13:55 ` Icenowy Zheng
2026-03-19 13:02 ` Jianmin Lv
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=16f3d7c5-d87c-e415-5efe-975d417e14d1@loongson.cn \
--to=lvjianmin@loongson.cn \
--cc=airlied@gmail.com \
--cc=chenhuacai@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jeffbai@aosc.io \
--cc=linux-kernel@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=wuqianhai@loongson.cn \
--cc=xry111@xry111.site \
/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
all inboxes | Powered by JetHome®