mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Armin Wolf <W_Armin@gmx.de>
To: 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>,
	"Hans de Goede" <hdegoede@redhat.com>
Subject: Re: New co-maintainer for ASUS driver
Date: Thu, 2 Oct 2025 21:09:22 +0200	[thread overview]
Message-ID: <6c0dca8e-cdd3-407b-8dc7-cf5414b37220@gmx.de> (raw)
In-Reply-To: <8128cd6b-50e3-464c-90c2-781f61c3963e@gmail.com>

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/
>
>

  reply	other threads:[~2025-10-02 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30 21:23 Denis Benato
2025-10-02 19:09 ` Armin Wolf [this message]
2025-10-03 14:01   ` Hans de Goede

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=6c0dca8e-cdd3-407b-8dc7-cf5414b37220@gmx.de \
    --to=w_armin@gmx.de \
    --cc=benato.denis96@gmail.com \
    --cc=hdegoede@redhat.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
all inboxes | Powered by JetHome®