public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Denis Benato <denis.benato@linux.dev>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	platform-driver-x86@vger.kernel.org,
	Hans de Goede <hansg@kernel.org>,
	"Limonciello, Mario" <mario.limonciello@amd.com>,
	"Luke D . Jones" <luke@ljones.dev>,
	Alok Tiwari <alok.a.tiwari@oracle.com>,
	Derek John Clark <derekjohn.clark@gmail.com>,
	Mateusz Schyboll <dragonn@op.pl>,
	porfet828@gmail.com, Denis Benato <benato.denis96@gmail.com>,
	Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH] platform/x86: asus-armoury: fix mini-led mode show
Date: Fri, 21 Nov 2025 20:57:21 +0100	[thread overview]
Message-ID: <5e21efe3-ea43-4d9c-9c22-dfe7a4a9f2aa@linux.dev> (raw)
In-Reply-To: <cb77645a-8779-6a91-4fc0-4c4871c643f3@linux.intel.com>


On 11/21/25 16:28, Ilpo Järvinen wrote:
> On Thu, 20 Nov 2025, Denis Benato wrote:
>
>> Perform the actual check of the mini-led mode against supported modes and do not return the first one regardless of the WMI devstate.
> I've taken this patch but I had to reformat the changelog. Preferrably use 
> up to 72 character long lines in the changelog (though I might not nitpick 
> from anything up to 75).
>
Thank you and sorry for the trouble, I'll try to keep that in mind and
commit from an editor that shows the border line :D


      reply	other threads:[~2025-11-21 19:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20  2:40 [PATCH] platform/x86: asus-armoury: fix mini-led mode show Denis Benato
2025-11-21 15:28 ` Ilpo Järvinen
2025-11-21 19:57   ` Denis Benato [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=5e21efe3-ea43-4d9c-9c22-dfe7a4a9f2aa@linux.dev \
    --to=denis.benato@linux.dev \
    --cc=alok.a.tiwari@oracle.com \
    --cc=benato.denis96@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=derekjohn.clark@gmail.com \
    --cc=dragonn@op.pl \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    --cc=mario.limonciello@amd.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=porfet828@gmail.com \
    /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