mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Armin Wolf <W_Armin@gmx.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: jlee@suse.com, Bugaddr@protonmail.com,
	Hans de Goede <hansg@kernel.org>,
	platform-driver-x86@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: acer-wmi: Ignore backlight event
Date: Tue, 18 Nov 2025 11:51:19 +0100	[thread overview]
Message-ID: <90093af0-7226-4ec4-b528-d6a23ea30c88@gmx.de> (raw)
In-Reply-To: <904d27a8-fcfc-35fd-153e-7cb48cc1fe4c@linux.intel.com>

Am 18.11.25 um 11:47 schrieb Ilpo Järvinen:

> On Tue, 18 Nov 2025, Armin Wolf wrote:
>
>> Am 18.11.25 um 09:11 schrieb Ilpo Järvinen:
>>
>>> On Mon, 17 Nov 2025 16:59:38 +0100, Armin Wolf wrote:
>>>
>>>> On the Acer Nitro AN515-58, the event 4 - 0 is send by the ACPI
>>>> firmware when the backlight up/down keys are pressed. Ignore this
>>>> event to avoid spamming the kernel log with error messages, as the
>>>> acpi-video driver already handles brightness up/down events.
>>>>
>>>>
>>> Thank you for your contribution, it has been applied to my local
>>> review-ilpo-fixes branch. Note it will show up in the public
>>> platform-drivers-x86/review-ilpo-fixes branch only once I've pushed my
>>> local branch there, which might take a while.
>> Thank you. I just noticed that i made a slight error inside the patch
>> description:
>> Tested-by: Reported-by: Bugaddr<Bugaddr@protonmail.com>
>>
>> Could you fix that up inside your branch?
> Hi,
>
> Hmm, I didn't notice it myself but think b4 did change it as this is
> what I've in the commit 444a9256f8d106e08a6bc2dc8ef28a8699e4b3ba:
>
>      Reported-by: Bugaddr <Bugaddr@protonmail.com>
>      Closes: https://bugaddr.tech/posts/2025-11-16-debugging-the-acer-nitro-5-an515-58-fn-f10-keyboard-backlight-bug-on-linux/#wmi-interface-issues
>      Tested-by: Bugaddr <Bugaddr@protonmail.com>
>      Signed-off-by: Armin Wolf <W_Armin@gmx.de>
>      Link: https://patch.msgid.link/20251117155938.3030-1-W_Armin@gmx.de
>      Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
>      Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
>
> ?

Strange, but the tags are indeed correct. In this case no further action seems to be necessary.

Thanks,
Armin Wolf


      reply	other threads:[~2025-11-18 10:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 15:59 Armin Wolf
2025-11-18  8:11 ` Ilpo Järvinen
2025-11-18 10:38   ` Armin Wolf
2025-11-18 10:47     ` Ilpo Järvinen
2025-11-18 10:51       ` Armin Wolf [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=90093af0-7226-4ec4-b528-d6a23ea30c88@gmx.de \
    --to=w_armin@gmx.de \
    --cc=Bugaddr@protonmail.com \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jlee@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --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®