mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Denis Benato <denis.benato@linux.dev>
Cc: LKML <linux-kernel@vger.kernel.org>,
	platform-driver-x86@vger.kernel.org,
	 Hans de Goede <hansg@kernel.org>,
	"Luke D . Jones" <luke@ljones.dev>,
	 Mateusz Schyboll <dragonn@op.pl>,
	Denis Benato <benato.denis96@gmail.com>
Subject: Re: [PATCH v4 0/3] platform/x86: asus-wmi: move keyboard control firmware attributes
Date: Wed, 14 Jan 2026 11:04:10 +0200 (EET)	[thread overview]
Message-ID: <cb403a32-f3a1-f92e-7974-08307641396d@linux.intel.com> (raw)
In-Reply-To: <2e1f5ce5-3647-4dff-b67e-327b0c1cb12e@linux.dev>

[-- Attachment #1: Type: text/plain, Size: 2368 bytes --]

On Tue, 13 Jan 2026, Denis Benato wrote:

> 
> On 1/13/26 15:02, Ilpo Järvinen wrote:
> > On Mon, 12 Jan 2026, Denis Benato wrote:
> >> On 1/3/26 00:43, Denis Benato wrote:
> >>> I was recently reading through the asusctl issue tracker and I found
> >>> out that some users have been having troubles with the keyboard RGB control
> >>> that was working before since the creation of asus-armoury and subequent
> >>> deprecation of old sysfs attributes.
> >>>
> >>> This patch series aims to re-introduce those attributes in asus-armoury
> >>> so that userspace tools can still control keyboard RGB lighting
> >>> without having to rely on deprecated asus-wmi attributes.
> >>>
> >>> In addition to that, since disabling OOBE is essential for controlling
> >>> LEDs on some models and it was incorrectly tied to deprecated attributes,
> >>> this patch series also fixes sending OOBE at probe time.
> >>>
> >>> Link: https://gitlab.com/asus-linux/asusctl/-/issues/619
> >>>
> >>> Regards,
> >>> Denis
> >> Hi Ilpo,
> >>
> >> I see no comments on this revision, did I sent it at wrong time?
> >> Should I resend some other time?
> >>
> >> Sorry for the question but I don't know if something went wrong,
> >> and if so what exactly.
> > Hi,
> >
> > Nothing is wrong, I've just had to spend time on finally processing 
> > some larger next series which were even older than yours. And we're only 1 
> > week past a holiday period which tend to add to delay.
> Oh okay, thank you for letting me know! I feared I repeated the error
> I made on the netdev list :)
> > Patchwork keeps track of pdx86 patches:
> >
> > https://patchwork.kernel.org/project/platform-driver-x86/list/
> >
> > If your patch is listed there, there's no need to ping as I'll get it it 
> > eventually (and it won't get forgotten).
> Understood! Sorry for the inconvenient :D
> > There's no "wrong time" to send a patch to pdx86, only that when the 
> > merge window is open, I might do processing of any patches during that 

In case it wasn't obvious, I meant: I might not do processing of any 
patches during the merge window.

> > time. But unlike some other subsystems, we don't disallow sending patches 
> > during merge window or any other time.
> >
> That's very good to know. Thank you very much, always very informative!
> 

-- 
 i.

  reply	other threads:[~2026-01-14  9:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-02 23:43 Denis Benato
2026-01-02 23:43 ` [PATCH v4 1/3] platform/x86: asus-wmi: explicitly mark more code with CONFIG_ASUS_WMI_DEPRECATED_ATTRS Denis Benato
2026-01-02 23:43 ` [PATCH v4 2/3] platform/x86: asus-wmi: fix sending OOBE at probe Denis Benato
2026-01-02 23:43 ` [PATCH v4 3/3] platform/x86: asus-armoury: add keyboard control firmware attributes Denis Benato
2026-01-12 20:49 ` [PATCH v4 0/3] platform/x86: asus-wmi: move " Denis Benato
2026-01-13 14:02   ` Ilpo Järvinen
2026-01-13 21:53     ` Denis Benato
2026-01-14  9:04       ` Ilpo Järvinen [this message]
2026-01-16 18:10         ` Denis Benato
2026-01-26  1:36 ` Denis Benato
2026-01-26 12:56   ` Ilpo Järvinen

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=cb403a32-f3a1-f92e-7974-08307641396d@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=benato.denis96@gmail.com \
    --cc=denis.benato@linux.dev \
    --cc=dragonn@op.pl \
    --cc=hansg@kernel.org \
    --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®