All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [Regression] ACPI: video: Change how we determine if brightness key-presses are handled #forregzbot
Date: Thu, 21 Jul 2022 13:29:43 +0200	[thread overview]
Message-ID: <de41c874-0f1b-e940-5c85-35fe79bc9a2a@leemhuis.info> (raw)
In-Reply-To: <baf81019-89a1-dc79-c80e-fe2dd1c8ee58@leemhuis.info>

TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.

On 13.07.22 07:54, Thorsten Leemhuis wrote:
> [CCing Hans, who authored 3a0cf7ab8d ("ACPI: video: Change how we
> determine if brightness key-presses are handled")]
> 
> On 13.07.22 07:27, Ben Greening wrote:
>> (resending because of HTML formatting)
>> Hi, I'm on Arch Linux and upgraded from kernel 5.18.9.arch1-1 to
>> 5.18.10.arch1-1. The brightness keys don't work as well as before.
>> Gnome had 20 degrees of brightness, now it's 10, and Xfce went from 10
>> to 5. Additionally, on Gnome the brightness keys are a little slow to
>> respond and there's a bit of a stutter. Don't know why Xfce doesn't
>> stutter, but halving the degrees of brightness for both makes me
>> wonder if each press is being counted twice.
>>
>> Reverting commit 3a0cf7ab8d in acpi_video.c and rebuilding
>> 5.18.10.arch1-1 fixed it.
> 
> BTW, in case someone gets slightly confused like I was here:
> 3a0cf7ab8d is a mainline commit that was backported to 5.18.y as
> 1ed81b354d8c recently.
> 
>> The laptop is a Dell Inspiron n4010 and I use "acpi_backlight=video"
>> to make the brightness keys work. Please let me know if there's any
>> hardware info you need.
>>
>> #regzbot introduced: 3a0cf7ab8d

Sorry, regzbot got confused by something, so let's mark this as resolved
manually:

#regzbot fixed-by: 5ad26161a371e4

  reply	other threads:[~2022-07-21 11:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13  5:27 [Regression] ACPI: video: Change how we determine if brightness key-presses are handled Ben Greening
2022-07-13  5:54 ` Thorsten Leemhuis
2022-07-21 11:29   ` Thorsten Leemhuis [this message]
2022-07-13  9:43 ` Hans de Goede
2022-07-13 13:08   ` Ben Greening
2022-07-13 13:29     ` Hans de Goede
2022-07-13 13:49       ` Hans de Goede
2022-07-13 23:56         ` Ben Greening
2022-07-14 19:38           ` Hans de Goede
2022-07-13 13:58       ` 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=de41c874-0f1b-e940-5c85-35fe79bc9a2a@leemhuis.info \
    --to=regressions@leemhuis.info \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.