archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <>
Subject: Re: Fwd: Re: amd | ASUS ROG Strix G513QY fails to resume from suspend [regression] (#2008) #forregzbot
Date: Fri, 13 May 2022 10:16:03 +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.

On 10.05.22 12:33, Thorsten Leemhuis wrote:
> On 10.05.22 10:37, Paul Menzel wrote:
>> Dear Linux regressions folks,
>> A user reported a regression [1], which also trickled down to the stable
>> series, for example between 5.15.13 and 5.15.14.
>> [1]:
> Many thx for forwarding. I'll add it to the tracking to ensure it's not
> forgotten:
> #regzbot introduced: 887f75cfd0da44c19dd
> #regzbot from: spin83
> #regzbot title: drm: amdgpu: ASUS ROG Strix G513QY fails to resume from
> suspend
> #regzbot link:
> Maybe the culprit is actually daf8de0874ab5b74b38a38726fdd3d, the report
> is not clear on that, I just picked the newest the reporter mentioned
> for now.

#regzbot introduced: eaa090538e8d21801c6d5f94590c3799e6a5
#regzbot fixed-by: a56f445f807b0276

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, 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-05-13  8:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2022-05-10  8:37 ` Fwd: Re: amd | ASUS ROG Strix G513QY fails to resume from suspend [regression] (#2008) Paul Menzel
2022-05-10 10:33   ` Thorsten Leemhuis
2022-05-10 14:20     ` Limonciello, Mario
2022-05-13  8:16     ` 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).