From: Denis Benato <denis.benato@linux.dev>
To: Jiri Kosina <jikos@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
Benjamin Tissoires <bentiss@kernel.org>,
"Luke D . Jones" <luke@ljones.dev>,
Mateusz Schyboll <dragonn@op.pl>,
Denis Benato <benato.denis96@gmail.com>,
Antheas Kapenekakis <lkml@antheas.dev>,
Connor Belli <connorbelli2003@gmail.com>
Subject: Re: [PATCH v5 0/5] HID: asus: security fixes and more hardware support
Date: Mon, 29 Jun 2026 20:00:10 +0200 [thread overview]
Message-ID: <ab282e6e-bc0a-4705-b25a-780d3ab33f5b@linux.dev> (raw)
In-Reply-To: <rr8s664r-5s34-1815-57ss-32p461sopp45@xreary.bet>
On 6/29/26 11:21, Jiri Kosina wrote:
> On Fri, 19 Jun 2026, Denis Benato wrote:
>
>> Hi all,
>>
>> I have added support for controlling the (way too bright) XG mobile
>> LEDs in hid-asus and added the i2c version of already supported
>> hardware that was probed only when it's a USB: these are two separate
>> features changes and are the only two that are not fixes for
>> pre-existing issue (see below).
>>
>> Auto-review bot has spotted a bunch of pre-existing problems alongside
>> problems in my own code therefore at this point I am going to fix the
>> more problems I can and including those fixes and improvements in this
>> patchset.
>>
>> For v4 I decided to follow Antheas' suggestion of reusing the existing
>> workqueue and by making it more generic I solved a good bunch of issues.
>>
>> The v5 iteration is simply me fixing a bunch of bugs in new code spotted
>> by the bot. Thanks for providing such a useful tool!
>>
>> On a side node this patchset has a few more warnings: specifically
>> "WARNING: Prefer kzalloc_obj over kzalloc with sizeof" but it's a false
>> positive as that would introduce sleeping calls in atomic contexts.
> Denis,
>
> thanks. Could you please flag which patches you'd prefer to go in still
> for 7.1 and which ones are not critical and could wait for 7.2? The whole
> lot is quite big.
Hi Jiri!
Patch 1 contains multiple fixes, mainly use of sleeping calls in atomic contexts:
I'd say slap it in 7.1 fixes.
Patch 2 is a minor improvement removing an OOM message to align the driver
to newer code where that would have been a flagged warning: probably a fix for
7.1 but there's no rush for this one.
Patch 3 is a logic fix, condition is very rare (not sure if even possible) but belongs
to 7.1 almost certainly.
Patch 4 new feature support: goes to 7.2.
Patch 5 unsure. It adds support to the backlight, but to properly do it I'll need
to wait for lamparray to be merged since autonomous mode must be disabled
to take effect. I'd say 7.2 just because of the missing lamparray. Merging in 7.1
has no downsides, yet IDK if putting in 7.1 violates some rule (probably yes?).
Please give a (very) quick read to the following link:
https://github.com/OpenGamingCollective/asusctl/issues/119#issuecomment-4723566635
This is something I am full of tickets for, probably we have reached the thousand
between discord, github and gitlab: very prominent issue and I'm eagerly waiting
for lamparray support to appear upstream.
Thanks,
Denis
> Thanks,
>
next prev parent reply other threads:[~2026-06-29 20:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 0:10 [PATCH v5 0/5] HID: asus: security fixes and more hardware support Denis Benato
2026-06-19 0:10 ` [PATCH v5 1/5] HID: asus: refactor the two workqueues and init sequence Denis Benato
2026-06-19 0:23 ` sashiko-bot
2026-06-19 0:11 ` [PATCH v5 2/5] HID: asus: remove extraneous OOM error Denis Benato
2026-06-19 0:11 ` [PATCH v5 3/5] HID: asus: fix a off-by-one in mcu_parse_version_string() validation Denis Benato
2026-06-19 0:11 ` [PATCH v5 4/5] HID: asus: add support for xgm led Denis Benato
2026-06-19 0:23 ` sashiko-bot
2026-06-19 0:11 ` [PATCH v5 5/5] HID: asus: add i2c entry for FA808UM and other TUFs Denis Benato
2026-06-29 9:21 ` [PATCH v5 0/5] HID: asus: security fixes and more hardware support Jiri Kosina
2026-06-29 18:00 ` Denis Benato [this message]
2026-06-29 20:21 ` Antheas Kapenekakis
2026-06-29 19:04 ` Denis Benato
2026-06-29 21:13 ` Antheas Kapenekakis
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=ab282e6e-bc0a-4705-b25a-780d3ab33f5b@linux.dev \
--to=denis.benato@linux.dev \
--cc=benato.denis96@gmail.com \
--cc=bentiss@kernel.org \
--cc=connorbelli2003@gmail.com \
--cc=dragonn@op.pl \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@antheas.dev \
--cc=luke@ljones.dev \
/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