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 215872] New: ath11k: QCA6390 firmware crashes after some time #forregzbot
Date: Mon, 20 Jun 2022 11:02:29 +0200	[thread overview]
Message-ID: <bbf11aa0-4c32-47c9-c9f9-5ae7089be177@leemhuis.info> (raw)
In-Reply-To: <9811c780-ea28-1461-6347-93a3cf218b6c@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 29.04.22 13:59, Thorsten Leemhuis wrote:
> On 21.04.22 22:07, bugzilla-daemon@kernel.org wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=215872
>>
>>             Bug ID: 215872
>>            Summary: ath11k: QCA6390 firmware crashes after some time
>>            Product: Drivers
>>            Version: 2.5
>>     Kernel Version: 5.17.3-arch1-1
>>           Hardware: x86-64
>>                 OS: Linux
>>               Tree: Mainline
>>             Status: NEW
>>           Severity: normal
>>           Priority: P1
>>          Component: Bluetooth
>>           Assignee: linux-bluetooth@vger.kernel.org
>>           Reporter: mail@kai-mast.de
>>         Regression: No
>>
>> Created attachment 300786
>>   --> https://bugzilla.kernel.org/attachment.cgi?id=300786&action=edit

Likely fixed, according to
https://bugzilla.kernel.org/show_bug.cgi?id=215872#c5

#regzbot fixed-by: d44e1dbda36ff

      reply	other threads:[~2022-06-20  9:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-215872-62941@https.bugzilla.kernel.org/>
2022-04-29 11:59 ` [Bug 215872] New: ath11k: QCA6390 firmware crashes after some time Thorsten Leemhuis
2022-06-20  9:02   ` 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=bbf11aa0-4c32-47c9-c9f9-5ae7089be177@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).