archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <>
To: Linus Torvalds <>
Cc: Linux Kernel Mailing List <>
Subject: Re: Linux 6.10-rc1
Date: Thu, 30 May 2024 09:48:09 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sun, May 26, 2024 at 03:31:45PM -0700, Linus Torvalds wrote:
> Ok, the merge window is over, and 6.10-rc1 is tagged and pushed out.
> This seems to be a regular-sized release, maybe even slightly on the
> smaller side. All the stats look fairly normal, but "normal" obviously
> means "much too big to post the shortlog", so below is - as always -
> just my "merge log" that gives an overview of who I've merged from
> with just the barest of descriptions.
> We don't have any new filesystems, and the xfs online repair work
> means that the bcachefs fixes aren't even the biggest filesystem
> change any more. But all of that is dwarfed by all the usual driver
> updates (and, as is tradition, GPU drivers are in a massive lead, with
> networking a distant second and everything else is relatively small).
> But we do have all the usual architecture updates, core cleanups and
> fixes, tooling and documentation updates.
> Please - let the testing commence,

From [1]:

Build results:
	total: 158 pass: 149 fail: 9
Failed builds:
Qemu test results:
	total: 470 pass: 466 fail: 4
Failed tests:
Unit test results:
	pass: 228437 fail: 0

The problems seen in those tests are all fixed with the following patches.

9ea60fe541a0 powerpc: Limit ARCH_HAS_KERNEL_FPU_SUPPORT to PPC64
005cc05a58df clk: sifive: Do not register clkdevs for PRCI clocks
71a1fd19a06c sysfs: Unbreak the build around sysfs_bin_attr_simple_read()
d304cefdad3a drm/nouveau/nvif: Avoid build error due to potential integer overflows
2afea78e811e scsi: mpi3mr: Use proper format specifier in mpi3mr_sas_port_add()

For anyone in details, those patches are available in the 'fixes' branch
of [2].


[2] git://

  parent reply	other threads:[~2024-05-30 16:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-26 22:31 Linux 6.10-rc1 Linus Torvalds
2024-05-27  7:50 ` Build regressions/improvements in v6.10-rc1 Geert Uytterhoeven
2024-05-27  8:21   ` Geert Uytterhoeven
2024-05-30 16:48 ` Guenter Roeck [this message]
2024-06-13 11:09 ` Linux 6.10-rc1 Pavel Machek
2024-06-13 16:17   ` Linus Torvalds
2024-06-14  9:02     ` Pavel Machek
2024-06-14 16:21       ` Linus Torvalds
2024-06-14 17:04         ` Linus Torvalds
2024-06-14 20:13           ` Pavel Machek
2024-06-14 20:24           ` Pavel Machek
2024-06-17  9:27           ` Pavel Machek
2024-06-19 10:43             ` Pavel Machek
2024-06-19 15:52               ` Linus Torvalds
2024-07-08 12:03                 ` Pavel Machek
2024-06-19 16:52               ` Gerhard Stoiber

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 \ \ \ \ \

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