linux-kernel - Re: New co-maintainer for ASUS driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <f44898fc-e745-477d-aa8c-b8df20c1db5a@kernel.org>
Date: Fri, 3 Oct 2025 16:01:55 +0200
From: Hans de Goede <hansg@...nel.org>
To: Armin Wolf <W_Armin@....de>, Denis Benato <benato.denis96@...il.com>,
 linux-kernel@...r.kernel.org
Cc: platform-driver-x86@...r.kernel.org, "Luke D . Jones" <luke@...nes.dev>,
 Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
Subject: Re: New co-maintainer for ASUS driver

Hi,

On 2-Oct-25 9:09 PM, Armin Wolf wrote:
> Am 30.09.25 um 23:23 schrieb Denis Benato:
> 
>> Hello,
>>
>> I am Denis Benato and I have been asked by my friend and person I estimate Luke to help him in his asus support effort and I gladly accepted.
>>
>> As a first step I have refined his asus-armoury as requested and resent it upsteam [1].
>>
>> With quite a few more work on the horizon for me, like the hid-ally driver, adding more models to the asus-armoury driver and working on the xg mobile interface I want to ask what's the best thing for me (and everybody) going forward?
>> Should I be added as a driver maintainer? Please, advice me on what to do next.
> 
> I suggest that when sending your next patch series regarding the asus-wmi driver, you include
> a patch adding yourself to the MAINTAINERS entry of the asus-wmi driver. This way contributors
> can automatically CC you on patches touching said driver.

+1 to this suggestion. I think that adding You (Denis) as
maintainer makes sense and this is the best way to do it.

Regards,

Hans