From: Thorsten Leemhuis <regressions@leemhuis.info>
To: regressions@lists.linux.dev
Subject: Re: [PATCH] Fix kbl_rt5663_rt5514_max98927 regression #forregzbot
Date: Thu, 3 Nov 2022 12:54:07 +0100 [thread overview]
Message-ID: <2cb07f70-c264-e7f3-06c8-9a1cb4149865@leemhuis.info> (raw)
In-Reply-To: <CAJD_bPKZMXUi+-eKNzcB_vmj8Nd_a94Md=Vo7Pp7Rb=-nxnfJQ@mail.gmail.com>
[Note: this mail is primarily send for documentation purposes and/or for
regzbot, my Linux kernel regression tracking bot. That's why I removed
most or all folks from the list of recipients, but left any that looked
like a mailing lists. These mails usually contain '#forregzbot' in the
subject, to make them easy to spot and filter out.]
On 02.11.22 22:09, Jason Montleon wrote:
> #regzbot introduced v5.19.17..v6.0-rc1
#regzbot invalid: this was added in the wrong way, closing this and
reading with another mail in a minute or two
(and yes, I need to modify regzbot to make this easier)
next prev parent reply other threads:[~2022-11-03 11:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 20:05 [PATCH] Fix kbl_rt5663_rt5514_max98927 regression Jason Montleon
2022-11-02 21:09 ` Jason Montleon
2022-11-03 11:54 ` Thorsten Leemhuis [this message]
2022-11-02 22:05 ` Pierre-Louis Bossart
2022-11-03 7:59 ` Takashi Iwai
2022-11-03 9:54 ` Charles Keepax
2022-11-03 11:13 ` Takashi Iwai
2022-11-03 13:11 ` [PATCH v2 1/2] ASoC: rt5514: fix legacy dai naming Jason Montleon
2022-11-03 13:11 ` [PATCH v2 2/2] ASoC: rt5677: " Jason Montleon
2022-11-03 13:19 ` [PATCH v2 1/2] ASoC: rt5514: " Mark Brown
2022-11-03 13:21 ` Takashi Iwai
2022-11-03 13:24 ` Takashi Iwai
2022-11-03 15:00 ` Thorsten Leemhuis
2022-11-03 13:20 ` [PATCH] Fix kbl_rt5663_rt5514_max98927 regression Jason Montleon
2022-11-03 11:57 ` [PATCH] Fix kbl_rt5663_rt5514_max98927 regression #forregzbot Thorsten Leemhuis
2022-11-05 10:13 ` Thorsten Leemhuis
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=2cb07f70-c264-e7f3-06c8-9a1cb4149865@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).