regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: Bug 215777 - ath11k: 5.17.x causes cpu soft-lock on xps13 9310 #forregzbot
Date: Mon, 9 May 2022 11:00:10 +0200	[thread overview]
Message-ID: <36be85b9-db4a-92c6-b26c-0a3e12353fbd@leemhuis.info> (raw)
In-Reply-To: <745e356a-0d4c-966b-66cb-e4067ca33d40@leemhuis.info>



On 21.04.22 11:51, Thorsten Leemhuis wrote:
> 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 fixed-by: 1f682dc9fb3790a
> #regzbot from: Dominik Förderer <dominik.foerderer@windeck-gymnasium.de>

Now also in a for-linus branch:

#regzbot fixed-by: bb300130e47fcefbe938f0

> On 08.04.22 10:20, Thorsten Leemhuis wrote:
>> Hi, this is your Linux kernel regression tracker speaking.
>>
>> About a week ago a regression was reported to bugzilla.kernel.org that
>> seems to be handled there already, nevertheless I'd like to add to the
>> tracking to ensure it's not forgotten.
>>
>> #regzbot introduced: 9dcf6808b253a72b2c90eed179863bf5fab7d68c
>> #regzbot from: dominik.foerderer@windeck-gymnasium.de
>> <dominik.foerderer@windeck-gymnasium.de>
>> #regzbot title: net: wifi: ath11k: 5.17.x causes cpu soft-lock on xps13
>> 9310
>> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215777
>>
>> See the ticket for details, there were a few replies already.
>>
>> 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.
>>

      reply	other threads:[~2022-05-09  9:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08  8:20 Bug 215777 - ath11k: 5.17.x causes cpu soft-lock on xps13 9310 Thorsten Leemhuis
2022-04-21  9:51 ` Bug 215777 - ath11k: 5.17.x causes cpu soft-lock on xps13 9310 #forregzbot Thorsten Leemhuis
2022-05-09  9:00   ` 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=36be85b9-db4a-92c6-b26c-0a3e12353fbd@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 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).