Linux Input/HID development
 help / color / mirror / Atom feed
From: "Linux regression tracking #update (Thorsten Leemhuis)"  <regressions@leemhuis.info>
To: Linux Regressions <regressions@lists.linux.dev>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Input Devices <linux-input@vger.kernel.org>
Subject: Re: Fwd: Regression: ALS/ACS stops working on amd-sfh
Date: Tue, 29 Aug 2023 15:43:57 +0200	[thread overview]
Message-ID: <d8758169-9f98-e050-61e5-7109176bb5d2@leemhuis.info> (raw)
In-Reply-To: <0ea231a1-e510-903d-22a0-998234426462@gmail.com>

[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]

On 04.08.23 14:45, Bagas Sanjaya wrote:
> Hi,
> 
> I notice a very concise regression report on Bugzilla [1]. That is,
> quoting from it:
> 
>> Since commit a33e5e393171ae8384d3381db5cd159ba877cfcb ("HID: amd_sfh: Fix illuminance value"), the in_illuminance_raw is 0 all the time.
>>
>> Before that commit, the ACS/ALS has normal value.
> 
> See Bugzilla for the full thread.
> 
> Anyway, I'm adding this regression to be tracked by regzbot:
> 
> #regzbot introduced: a33e5e393171ae https://bugzilla.kernel.org/show_bug.cgi?id=217762
> #regzbot title: Fixing in_illuminance_raw value hard-codes ACS/ALS to 0

#regzbot inconclusive: developer closed ticket as RESOLVED
UNREPRODUCIBLE (likely "firmware bug for your platform" and reporter
didn't complain
#regzbot ignore-activity

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
That page also explains what to do if mails like this annoy you.


      reply	other threads:[~2023-08-29 13:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 12:45 Fwd: Regression: ALS/ACS stops working on amd-sfh Bagas Sanjaya
2023-08-29 13:43 ` Linux regression tracking #update (Thorsten Leemhuis) [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=d8758169-9f98-e050-61e5-7109176bb5d2@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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