linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)"  <regressions@leemhuis.info>
To: Chuanhong Guo <gch981213@gmail.com>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux kernel regressions list <regressions@lists.linux.dev>
Subject: [regression] Bug 217394 - IRQ override skipping breaks the Aya Neo Air Plus 6800U keyboard buttons
Date: Wed, 3 May 2023 14:58:30 +0200	[thread overview]
Message-ID: <01ea5c8e-ed2f-7568-f6ed-896329e7b673@leemhuis.info> (raw)

Hi, Thorsten here, the Linux kernel's regression tracker.

I noticed a regression report in bugzilla.kernel.org. As many (most?)
kernel developers don't keep an eye on it, I decided to forward it by mail.

Chuanhong Guo, apparently it's cause by a change of yours.

Note, you have to use bugzilla to reach the reporter, as I sadly[1] can
not CCed them in mails like this.

Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=217394 :

>  Matthew 2023-05-03 02:28:33 UTC
> 
> Reverting the changes found in this patch fixes the issue:
>> https://lore.kernel.org/all/20220712020058.90374-1-gch981213@gmail.com/
> 
> With that patch the AT Translated Set 2 Keyboard doesn't show up with the evtest and is not usable.
> 
> Hardware: 
> 
> Aya Neo Air Plus
> AMD Ryzen 7 6800U
See the ticket for more details.

BTW: there apparently is another IRQ override needed for a different
machine. See https://bugzilla.kernel.org/show_bug.cgi?id=216804#c8 for
details (ignore the comments before that, the quirk entry for that
machine was merged; comment 8 and all related to it really should have a
separate bug; that's also why this partly fall through the cracks here
:-/ ). The user is currently trying to create a patch.


[TLDR for the rest of this mail: I'm adding this report to the list of
tracked Linux kernel regressions; the text you find below is based on a
few templates paragraphs you might have encountered already in similar
form.]

BTW, let me use this mail to also add the report to the list of tracked
regressions to ensure it's doesn't fall through the cracks:

#regzbot introduced: 9946e39fe8d0
https://bugzilla.kernel.org/show_bug.cgi?id=217394
#regzbot title: acpi: IRQ override quirk needed for Aya Neo Air Plus 6800U
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (e.g. the buzgzilla ticket and maybe this mail as well, if
this thread sees some discussion). See page linked in footer for details.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

[1] because bugzilla.kernel.org tells users upon registration their
"email address will never be displayed to logged out users"

             reply	other threads:[~2023-05-03 12:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 12:58 Linux regression tracking (Thorsten Leemhuis) [this message]
2023-05-03 16:11 ` [regression] Bug 217394 - IRQ override skipping breaks the Aya Neo Air Plus 6800U keyboard buttons Limonciello, Mario
2023-05-03 19:00   ` Dmitry Torokhov
2023-05-06  6:47     ` Thorsten Leemhuis
2023-05-07 12:45       ` Mario Limonciello
2023-05-08 15:17         ` Dmitry Torokhov
2023-05-06  8:25   ` Chuanhong Guo
2023-05-07 12:41     ` Mario Limonciello
2023-05-07 14:55       ` Matthew Anderson

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=01ea5c8e-ed2f-7568-f6ed-896329e7b673@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=gch981213@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=rafael.j.wysocki@intel.com \
    --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).