X86 platform drivers
 help / color / mirror / Atom feed
From: "Seyed Mohammad Mahdi Hosseini" <i@smmh.dev>
To: eugene.wolferz@gmail.com, denis.benato@linux.dev
Cc: corentin.chary@gmail.com, luke@ljones.dev, hansg@kernel.org,
	ilpo.jarvinen@linux.intel.com,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: asus-nb-wmi: Ignore spurious 0xe5 events on GU605MY
Date: Fri, 30 Oct 2026 01:47:14 +0100	[thread overview]
Message-ID: <c56ca832d450480df59096daeae35ab3@smmh.dev> (raw)
In-Reply-To: <CADQe2ZeEJEgE3AoXCtPNAvrggjJmG4WJh=O6++GS+ipRXaVgWQ@mail.gmail.com>

On Mon, 19 Oct 2026 22:28 UTC, Evgeny Volferts wrote:
> I also noticed the related patch series from Seyed Mohammad Mahdi
> Hosseini, which proposes the same global KE_IGNORE approach:
>
> https://lore.kernel.org/platform-driver-x86/cover.1791672579.git.i@smmh.dev/
>
> Since my patch was submitted first, I would be happy to prepare a v2
> using the global KE_IGNORE approach, incorporating your feedback.

Hi Evgeny,

Thanks for pointing to my series. Its patch 1 is the global ignore
Denis suggested, a single KE_IGNORE entry for 0xE5 in the keymap:

https://lore.kernel.org/r/d3871d83ee3f5eea3900d8bc0da1de764a8fc2ec.1791672579.git.i@smmh.dev

I am fine with either version going in, your v2 or my patch 1,
whichever Ilpo and Denis prefer to take.

Patch 2 of my series (0x4F, Fn+Windows) does not depend on 0xE5 and
applies on its own either way.

Best regards,
Seyed Mohammad Mahdi Hosseini

  reply	other threads:[~2026-10-30  0:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 16:30 [PATCH] platform/x86: asus-nb-wmi: Ignore spurious 0xe5 events on GU605MY Evgeny Volferts
2026-10-19 22:12 ` Denis Benato
2026-10-19 22:28   ` Евгений Вольферц
2026-10-30  0:47     ` Seyed Mohammad Mahdi Hosseini [this message]
2026-10-20 11:11   ` Ilpo Järvinen
2026-10-20 11:27     ` Denis Benato

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=c56ca832d450480df59096daeae35ab3@smmh.dev \
    --to=i@smmh.dev \
    --cc=corentin.chary@gmail.com \
    --cc=denis.benato@linux.dev \
    --cc=eugene.wolferz@gmail.com \
    --cc=hansg@kernel.org \
    --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