Re: [PATCH] MAINTAINERS: add myself and Barry to dma_map_benchmark maintainers
From: Qinxin Xia
Date: Sun Sep 28 2025 - 02:11:20 EST
On 2025/9/26 14:59:36, Barry Song <21cnbao@xxxxxxxxx> wrote:
On Fri, Sep 26, 2025 at 6:09 AM Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx> wrote:Hello Barry,
On 9/25/25 07:11, Qinxin Xia wrote:
On 2025/9/22 20:20:39, Marek Szyprowski <m.szyprowski@xxxxxxxxxxx> wrote:
On 22.09.2025 01:50, Barry Song wrote:I'll send V2 in the next version to fix some of the review comments of V1, and maybe there's some discussion about V2, I think shuah can deal with the patches of MAINTAINERS first :)
On Fri, Sep 19, 2025 at 2:17 AM Marek Szyprowski
<m.szyprowski@xxxxxxxxxxx> wrote:
On 17.09.2025 03:17, Qinxin Xia wrote:Thanks!
Since Chenxiang has left HiSilicon, Barry and I will jointlyAcked-by: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>
maintain this module.
Signed-off-by: Qinxin Xia <xiaqinxin@xxxxxxxxxx>
Marek, would you rather merge this into the dma-mapping tree
instead of ACKing it, or would you prefer it to go through
a different tree?
I expected it to be taken by Shuah, as she is responsible for the
tools/testing/selftests/ directory, where the dma tests are still placed.
Best regards
I can take this patch through my tree. Are you sending v2?
Qinxin mentioned a v2 for the tools/dma modification[1], but there’s
no need for a v2 of the maintainer patch. Could you please pull this
one into your tree? Thanks!
Qinxin, could you please avoid mixing topics, as it can be
quite confusing?
[1] https://lore.kernel.org/lkml/20250814133527.2679261-2-xiaqinxin@xxxxxxxxxx/
Thanks
Barry
I'm so sorry for the confusion.
The reason is that the movement in the tools/dma modification involves
modifications to the MAINTAINERS and decisions about which tree to pull
into. So, my original intention was to sync up with both you and Marek
on this: first update the MAINTAINERS file, and then proceed with
uploading the changes to tools/dma. Maybe I should mention this in the
last version of tools/dma modification.
Thank you so much for your understanding.