linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Corentin Chary <corentin.chary@gmail.com>,
	Guilhem Lettron <guilhem@lettron.fr>
Cc: Linux Input Devices <linux-input@vger.kernel.org>,
	ACPI Asus <acpi4asus-user@lists.sourceforge.net>,
	Linux x86 Platform Drivers  <platform-driver-x86@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>
Subject: Fwd: 6.5 - 6.4.7 Regression : ASUS UM5302TA Keyboard don't work
Date: Sun, 30 Jul 2023 09:41:40 +0700	[thread overview]
Message-ID: <bdc6cb4d-a853-72b2-b132-989b64740ad9@gmail.com> (raw)

Hi,

I notice a regression report on Bugzilla [1]. Quoting from it:

> On a kernel 6.4.5 and less, the keyboard is working fine.
> 
> Beginning with 6.5 rc1 and 6.4.7 any key don't respond.
> 
> [    0.668850] input: ASUE140D:00 04F3:31B9 Keyboard as /devices/platform/AMDI0010:01/i2c-1/i2c-ASUE140D:00/0018:04F3:31B9.0001/input/input5
> ...
> [    1.930328] input: ASUE140D:00 04F3:31B9 Keyboard as /devices/platform/AMDI0010:01/i2c-1/i2c-ASUE140D:00/0018:04F3:31B9.0001/input/input13

See Bugzilla for the full thread.

Anyway, I'm adding this regression to regzbot:

#regzbot introduced: v6.4..v6.5-rc1 https://bugzilla.kernel.org/show_bug.cgi?id=217726
#regzbot title: ASUE140D:00 04F3:31B9 doesn't respond to input

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217726

-- 
An old man doll... just what I always wanted! - Clara

             reply	other threads:[~2023-07-30  2:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-30  2:41 Bagas Sanjaya [this message]
2023-07-30  4:49 ` Fwd: 6.5 - 6.4.7 Regression : ASUS UM5302TA Keyboard don't work Linux regression tracking (Thorsten Leemhuis)
2023-07-30 18:07   ` Mario Limonciello
2023-08-04 15:26   ` August Wikerfors
2023-08-05 13:09     ` Hans de Goede
2023-08-05 13:37       ` Linux regression tracking (Thorsten Leemhuis)
2023-08-06 15:19       ` Hans de Goede

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=bdc6cb4d-a853-72b2-b132-989b64740ad9@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=corentin.chary@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=guilhem@lettron.fr \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=regressions@lists.linux.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;
as well as URLs for NNTP newsgroup(s).