All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: Thread for updating minor properties of tracked regressions [consider ignoring it!]
Date: Sun, 12 May 2024 08:59:34 +0200	[thread overview]
Message-ID: <0834b74a-b360-4404-994b-7f20c89d7257@leemhuis.info> (raw)
In-Reply-To: <fb0c84ab-5407-4a17-bbe7-832d8c4a51da@leemhuis.info>



On 09.03.24 11:18, Thorsten Leemhuis wrote:
> Hi! This is the start of a thread I'll use for updating minor properties
> of regressions tracked by regzbot. Consider telling your mailer to
> ignore this thread, the replies are unlikely to be of relevance for you,
> but done here to ensure a public paper trail.

#regzbot report:
https://lore.kernel.org/linux-usb/9efbd569-7059-4575-983f-0ea30df41871@suse.com/
#regzbot fix: c78c3644b772e356

#regzbot report: https://lore.kernel.org/all/87o79cjjik.fsf@kernel.org/
#regzbot introduced: v6.9-rc3..v6.9-rc6
#regzbot summary: x86: mitigations: suspend stress test stalls within 30
minutes

#regzbot report: https://lore.kernel.org/netdev/Zh/tyozk1n0cFv+l@euler/
#regzbot resolve: afaics irrelevant [Thorsten]

#regzbot report: https://bugzilla.kernel.org/show_bug.cgi?id=218759
#regzbot introduced: f3a052391822
#regzbot fix: cpufreq: amd-pstate: fix the highest frequency issue which
limit performance

#regzbot report:
https://lore.kernel.org/linux-wireless/87wmo0k71i.fsf@kernel.org/
#regzbot fix: wifi: ath11k: move power type check to ASSOC stage when
connecting to 6 GHz AP

  parent reply	other threads:[~2024-05-12  6:59 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-09 10:18 Thread for updating minor properties of tracked regressions [consider ignoring it!] Thorsten Leemhuis
2024-03-09 10:34 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-09 12:39 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-11 13:12 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-12 12:27 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-19  8:57 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-23 12:34 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-24 13:04 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-26 13:37 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-29 10:00 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-02 14:27 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-05  9:35 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-09  7:36 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-11 17:27 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-14  7:01 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-16  9:29 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-17  8:56 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-18  9:16 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-21 11:23 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-21 13:53 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-21 16:49 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-22 17:36 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-24 17:12 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-26  9:05 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-29  8:20 ` Christian Heusel
2024-04-29 10:01   ` Linux regression tracking (Thorsten Leemhuis)
2024-04-30  5:02 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-02  5:38 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-04  9:20 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-05 13:40 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-09 10:34 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-10  8:29 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-12  6:59 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2024-05-18  9:39 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-19 12:43 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-21 13:26 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-22 12:35 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-23 11:49 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-24 13:16 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-26 10:16 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-26 17:18 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-26 17:23 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-28  9:13 ` Linux regression tracking (Thorsten Leemhuis)
  -- strict thread matches above, loose matches on Subject: below --
2024-03-21 10:40 Linux regression tracking (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=0834b74a-b360-4404-994b-7f20c89d7257@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.