From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
scott.branden@broadcom.com
Subject: Re: 5.15 Linux Regression in sound hda
Date: Wed, 10 Nov 2021 20:02:13 +0100 [thread overview]
Message-ID: <e0f4c645-3e37-ace2-196a-6230ecf81c87@leemhuis.info> (raw)
In-Reply-To: <063e2397-7edb-5f48-7b0d-618b938d9dd8@broadcom.com>
On 09.11.21 22:12, Scott Branden wrote:
> I'm reporting a new WARN_ON in sound/hda/hdac_bus.c that was not present
> in 5.15. Sorry, I don't have time to bisect this right now but report
> is below.
Scott, thx for CCing me. A fix seem to be on the horizon already, but to
be sure this issue doesn't fall through the cracks unnoticed I'm adding
it to regzbot, the Linux kernel regression tracking bot:
#regzbot ^introduced v5.15..
#regzbot ignore-activity
I removed everyone else from the To or CC, as this mail is meaningless
for the others.
Ciao, Thorsten, your Linux kernel regression tracker.
parent reply other threads:[~2021-11-10 19:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <063e2397-7edb-5f48-7b0d-618b938d9dd8@broadcom.com>]
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=e0f4c645-3e37-ace2-196a-6230ecf81c87@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=scott.branden@broadcom.com \
/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).