archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <>
To: "" <>
	Linux Kernel Mailing List <>
Subject: Re: Bug 215744 - input from the accelerometer disappeared, regression on amd_sfh on kernel 5.17 #forregzbot
Date: Fri, 29 Apr 2022 13:34:08 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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.

#regzbot invalid: bios bug and reporter seems to be satisfied by
resolving this with a bios update

On 01.04.22 10:06, Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker.
> I noticed a regression report in that afaics nobody
> acted upon since it was reported about a week ago, that's why I decided
> to forward it to the lists and all people that seemed to be relevant
> here. It looks to me like this is something for Basavaraj, as it seems
> to be caused by	b300667b33b2 ("HID: amd_sfh: Disable the interrupt for
> all command"). But I'm not totally sure, I only looked briefly into the
> details. Or was this discussed somewhere else already? Or even fixed?
> To quote from :
>>  Marco 2022-03-25 15:22:19 UTC
>> After updating to 5.17, the input from the accelerometer disappeared, completely. No devices available from IIO tree. First bad commit causing it is Reverting this and the the other two on top fixed this. Tried to not revert only the above mentioned commit, but it's still not working.
>> Marco.
> Anyway, to get this tracked:
> #regzbot introduced: b300667b33b2b5a2c8e5f8f22826befb3d7f4
> #regzbot from: Marco <>
> #regzbot title: input: hid: input from the accelerometer disappeared due
> to changes to amd_sfh
> #regzbot link:
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> P.S.: As the Linux kernel's regression tracker I'm getting a lot of
> reports on my table. I can only look briefly into most of them and lack
> knowledge about most of the areas they concern. I thus unfortunately
> will sometimes get things wrong or miss something important. I hope
> that's not the case here; if you think it is, don't hesitate to tell me
> in a public reply, it's in everyone's interest to set the public record
> straight.

      parent reply	other threads:[~2022-04-29 11:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01  8:06 Bug 215744 - input from the accelerometer disappeared, regression on amd_sfh on kernel 5.17 Thorsten Leemhuis
2022-04-01 19:47 ` Basavaraj Natikar
2022-04-04  6:35   ` Thorsten Leemhuis
2022-04-04  7:18     ` Basavaraj Natikar
2022-04-04  7:25       ` Thorsten Leemhuis
2022-04-04 13:53         ` Thorsten Leemhuis
2022-04-04 14:04           ` Basavaraj Natikar
     [not found]             ` <>
2022-04-04 17:40               ` Marco
2022-04-17 17:16                 ` Marco
2022-04-21  9:15                   ` Benjamin Tissoires
2022-04-21  9:24                     ` Basavaraj Natikar
2022-04-29 11:34 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).