regressions.lists.linux.dev archive mirror
 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, 14 Apr 2024 09:01:23 +0200	[thread overview]
Message-ID: <854a1d63-8e10-4214-92c4-e4dbf9726a92@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/all/ZaQS5x-XK08Jre6I@smile.fi.intel.com/
#regzbot introduced: f49449fbc21e7e9550a
#regzbot summary: usb: gadget: u_ether: ether setup broken

#regzbot report: https://lore.kernel.org/all/ZhFl6xueHnuVHKdp@nuc/
#regzbot introduced: d2689b6a86b9
#regzbot summary: ax88179_178a assigns the same MAC address to all USB
network interfaces
#regzbot fix: net: usb: ax88179_178a: avoid writing the mac address
before first reading
#regzbot monitor:
https://lore.kernel.org/all/20240410095603.502566-1-jtornosm@redhat.com/

#regzbot report: https://lore.kernel.org/all/20240413024956.488d474e@yea/
#regzbot introduced: 4461438a8405e800f90e
#regzbot duplicate:
https://lore.kernel.org/all/20240403173059.GJZg2SUwS8MXw7CdwF@fat_crate.local/
#regzbot summary: x86/retpoline: MITIGATION_RETHUNK causes boot problems
on x86-32 machines

#regzbot report:
https://lore.kernel.org/all/878r1ibpdn.fsf@all.your.base.are.belong.to.us/
#regzbot introduced: c604110e662a
#regzbot summary: riscv32 EXT4 splat

  parent reply	other threads:[~2024-04-14  7:01 UTC|newest]

Thread overview: 31+ 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) [this message]
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-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=854a1d63-8e10-4214-92c4-e4dbf9726a92@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).