From: Hans de Goede <hansg@kernel.org>
To: Armin Wolf <W_Armin@gmx.de>,
Denis Benato <benato.denis96@gmail.com>,
linux-kernel@vger.kernel.org
Cc: platform-driver-x86@vger.kernel.org,
"Luke D . Jones" <luke@ljones.dev>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: New co-maintainer for ASUS driver
Date: Fri, 3 Oct 2025 16:01:55 +0200 [thread overview]
Message-ID: <f44898fc-e745-477d-aa8c-b8df20c1db5a@kernel.org> (raw)
In-Reply-To: <6c0dca8e-cdd3-407b-8dc7-cf5414b37220@gmx.de>
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
prev parent reply other threads:[~2025-10-03 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 21:23 New co-maintainer for ASUS driver Denis Benato
2025-10-02 19:09 ` Armin Wolf
2025-10-03 14:01 ` Hans de Goede [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=f44898fc-e745-477d-aa8c-b8df20c1db5a@kernel.org \
--to=hansg@kernel.org \
--cc=W_Armin@gmx.de \
--cc=benato.denis96@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=platform-driver-x86@vger.kernel.org \
/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