All of
 help / color / mirror / Atom feed
From: Linus Torvalds <>
To: "Regzbot (on behalf of Thorsten Leemhuis)" <>
Cc: LKML <>,
	 Linux regressions mailing list <>
Subject: Re: Linux regressions report for mainline [2022-11-27]
Date: Sun, 27 Nov 2022 12:30:41 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sun, Nov 27, 2022 at 9:32 AM Regzbot (on behalf of Thorsten
Leemhuis) <> wrote:
> Hi Linus! Below is a slightly edited report from regzbot listing all
> regression from this cycle that the bot and I are currently aware of.

Thanks. This looks fairly reasonable (assuming I get that networking
fix next week - the others are in the "won't delay a release" category
as far as I'm concerned).

But it looks like I'll be doing not just an rc7 but an rc8 regardless
of the current regression state just because I still see too much


      reply	other threads:[~2022-11-27 20:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-27 17:32 Linux regressions report for mainline [2022-11-27] Regzbot (on behalf of Thorsten Leemhuis)
2022-11-27 20:30 ` Linus Torvalds [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \

* 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.