From: Bibo Mao <maobibo@loongson.cn>
To: zhoumin <zhoumin@loongson.cn>, Patrick Robb <probb@iol.unh.edu>
Cc: thomas@monjalon.net, dev@dpdk.org, ci@dpdk.org
Subject: Re: [PATCH v1] maintainers: update for LoongArch
Date: Thu, 16 Oct 2025 20:40:54 +0800 [thread overview]
Message-ID: <c7f0e0cc-bd06-4474-2e7e-410c302b222e@loongson.cn> (raw)
In-Reply-To: <fec69d04-4ba6-2378-61c9-15be790bb8e5@loongson.cn>
On 2025/10/16 下午8:30, zhoumin wrote:
> Hi Patrick Robb,
>
> Yes, Bibo will also be responsible for maintaining the LoongArch CI
> testing going forward.
I will be responsible for maintaining the LoongArch CI also,
and best wishes and thanks for contribution for Min Zhou.
Regards
Bibo Mao
>
> On Thu, Oct 16, 2025 at 7:32 PM, Patrick Robb wrote:
>> Hi Min Zhou,
>>
>> Will Bibi be responsible for maintaining the Loongarch CI testing
>> going forward, or are you retaining that responsibility? Thanks.
>>
>> On Thu, Oct 16, 2025 at 5:46 AM Min Zhou <zhoumin@loongson.cn
>> <mailto:zhoumin@loongson.cn>> wrote:
>>
>> Update maintainers for LoongArch architecture.
>>
>> Signed-off-by: Min Zhou <zhoumin@loongson.cn
>> <mailto:zhoumin@loongson.cn>>
>> Signed-off-by: Bibo Mao <maobibo@loongson.cn
>> <mailto:maobibo@loongson.cn>>
>> ---
>> MAINTAINERS | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 1a2729be66..7abe482e7d 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -320,7 +320,7 @@ F: examples/*/*_neon.*
>> F: examples/common/neon/
>>
>> LoongArch
>> -M: Min Zhou <zhoumin@loongson.cn <mailto:zhoumin@loongson.cn>>
>> +M: Bibo Mao <maobibo@loongson.cn <mailto:maobibo@loongson.cn>>
>> F: config/loongarch/
>> F: doc/guides/linux_gsg/cross_build_dpdk_for_loongarch.rst
>> F: lib/eal/loongarch/
>> --
>> 2.27.0
>>
prev parent reply other threads:[~2025-10-16 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 9:09 Min Zhou
2025-10-16 11:32 ` Patrick Robb
2025-10-16 12:30 ` zhoumin
2025-10-16 12:40 ` Bibo Mao [this message]
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=c7f0e0cc-bd06-4474-2e7e-410c302b222e@loongson.cn \
--to=maobibo@loongson.cn \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
--cc=zhoumin@loongson.cn \
/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).