From: Linus Torvalds <torvalds@linux-foundation.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: Linux 6.2-rc5
Date: Sun, 22 Jan 2023 11:17:58 -0800 [thread overview]
Message-ID: <CAHk-=wgkzFgUsU+M55xSzG3hzYajDOqXFzDwnoyRzwKDbEmzag@mail.gmail.com> (raw)
In-Reply-To: <8ec65f01-89fe-bd6f-a2c2-f4dfc0555cc2@leemhuis.info>
On Sun, Jan 22, 2023 at 5:49 AM Linux kernel regression tracking
(Thorsten Leemhuis) <regressions@leemhuis.info> wrote:
>
> Huh, a -rc on Saturday evening? That's unusual.
Heh. It's my wedding anniversary today.. Not that I won't sit in front
of the computer anyway, but I didn't want to have anything actually
pending.
> But nevertheless there is one thing I want to bring up, even if -rc5 is
> already out: Vlastimil asked me explicitly to highlight ```Revert
> "mm/compaction: fix set skip in fast_find_migrateblock"```[1] in my
> weekly report[2], as me would prefer if that patch could head to
> mainline and especially stable rather sooner than later.
Ok, I assume I'll get it from Andrew one of these days. Thanks for the heads-up.
I'm going to do an rc8 regardless, so we're not quite at the end of
the release yet.
Linus
next prev parent reply other threads:[~2023-01-22 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 0:44 Linux 6.2-rc5 Linus Torvalds
2023-01-22 11:51 ` Build regressions/improvements in v6.2-rc5 Geert Uytterhoeven
2023-01-22 13:49 ` Linux 6.2-rc5 Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-22 19:17 ` Linus Torvalds [this message]
2023-01-22 21:51 ` Guenter Roeck
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='CAHk-=wgkzFgUsU+M55xSzG3hzYajDOqXFzDwnoyRzwKDbEmzag@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=vbabka@suse.cz \
/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.