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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <6c0dca8e-cdd3-407b-8dc7-cf5414b37220@gmx.de>
Date: Thu, 2 Oct 2025 21:09:22 +0200
From: Armin Wolf <W_Armin@....de>
To: 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>,
 Hans de Goede <hdegoede@...hat.com>
Subject: Re: New co-maintainer for ASUS driver

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.

Thanks,
Armin Wolf

> Thanks for your time and understanding,
> Denis Benato
>
> [1] https://lore.kernel.org/all/20250813165620.1131127-1-benato.denis96@gmail.com/
>
>