From: Lizhi Hou <lizhi.hou@amd.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: <dri-devel@lists.freedesktop.org>,
<jacek.lawrynowicz@linux.intel.com>,
<linux-kernel@vger.kernel.org>, <ogabbay@kernel.org>,
<quic_jhugo@quicinc.com>, Min Ma <mamin506@gmail.com>
Subject: Re: [PATCH v3] MAINTAINERS: Update Min Ma's email for AMD XDNA driver
Date: Thu, 4 Sep 2025 10:15:42 -0700 [thread overview]
Message-ID: <b2cb52b1-9bcc-b77a-ed9b-cf3dbaea1a71@amd.com> (raw)
In-Reply-To: <67138df3-115d-94cb-005f-84f6f56f5986@amd.com>
Hi Lucas
I got a dim error when applying this patch. Could you take a look? Maybe
there is not a maintainer for MAINTAINERS? :)
dim: ERROR: a12586e4e737 ("MAINTAINERS: Update Min Ma's email for AMD
XDNA driver"): Mandatory Maintainer Acked-by missing., aborting
Thanks,
Lizhi
On 9/2/25 12:47, Lizhi Hou wrote:
> Reviewed-by: Lizhi Hou <lizhi.hou@amd.com>
>
> On 8/30/25 17:12, Min Ma wrote:
>> I recently left AMD and would like to continue participating in
>> the review and maintenance of the XDNA driver using my personal
>> email address.
>>
>> Signed-off-by: Min Ma <mamin506@gmail.com>
>> ---
>> MAINTAINERS | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 10850512c118..6eefa494000c 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -1231,7 +1231,7 @@ F: drivers/spi/spi-amd.c
>> F: drivers/spi/spi-amd.h
>> AMD XDNA DRIVER
>> -M: Min Ma <min.ma@amd.com>
>> +M: Min Ma <mamin506@gmail.com>
>> M: Lizhi Hou <lizhi.hou@amd.com>
>> L: dri-devel@lists.freedesktop.org
>> S: Supported
next prev parent reply other threads:[~2025-09-04 17:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 6:38 [PATCH] MAINTAINERS: Update Min Ma's email for AMD XDNA driver Min Ma
2025-08-22 16:42 ` Lizhi Hou
2025-08-26 6:11 ` Min Ma
2025-08-29 6:36 ` [PATCH v2] " Min Ma
2025-08-29 15:52 ` Lizhi Hou
2025-08-31 0:12 ` [PATCH v3] " Min Ma
2025-09-02 19:47 ` Lizhi Hou
2025-09-04 17:15 ` Lizhi Hou [this message]
2025-09-04 17:50 ` Lucas De Marchi
2025-09-04 23:07 ` Lizhi Hou
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=b2cb52b1-9bcc-b77a-ed9b-cf3dbaea1a71@amd.com \
--to=lizhi.hou@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=mamin506@gmail.com \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.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