mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	David Gow <davidgow@google.com>
Subject: Re: Linux 6.17-rc5
Date: Tue, 9 Sep 2025 08:27:58 -0700	[thread overview]
Message-ID: <aMBHfv3dQPZ0iLSM@google.com> (raw)
In-Reply-To: <f957c6e8-98bf-488d-a898-39265a7661d9@roeck-us.net>

CC David, Thomas

On Mon, Sep 08, 2025 at 05:50:24PM -0700, Guenter Roeck wrote:
> Nothing much to report on the testing side.
> 
> Build results:
> 	total: 162 pass: 162 fail: 0
> Qemu test results:
> 	total: 637 pass: 637 fail: 0
> Unit test results:
> 	pass: 640105 fail: 650
> 
> Same story as before. The unit test failures are [still] due to the new
> irq tests. Brian submitted a set of patches fixing the problem a couple
> of weeks ago. They may or may not make it into this release - we'll see.
> Cc Brian in case he has an update.

Thomas has all the fixes queued up in tip/irq/core. Presumably that
means they'll go to 6.18. They're test-only fixes, so they don't affect
the behavior of the kernel itself; I don't know the policies around
that, and whether they should be prioritized for 6.17.

I think this is the full set of related changes that aren't in mainline
yet:

c9163915a93d genirq/test: Fix depth tests on architectures with NOREQUEST by default.
f8a44f9babd0 genirq/test: Select IRQ_DOMAIN
59405c248ace genirq/test: Factor out fake-virq setup
988f45467f13 genirq/test: Fail early if interrupt request fails
0c888bc86d67 genirq/test: Depend on SPARSE_IRQ
add03fdb9d52 genirq/test: Drop CONFIG_GENERIC_IRQ_MIGRATION assumptions
8ad25ebfa70e genirq/test: Ensure CPU 1 is online for hotplug test

Brian

  reply	other threads:[~2025-09-09 15:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07 22:25 Linus Torvalds
2025-09-09  0:50 ` Guenter Roeck
2025-09-09 15:27   ` Brian Norris [this message]
2025-09-12  6:24 ` Commit Links [was: Linux 6.17-rc5] Jiri Slaby
2025-09-12 19:14   ` Al Viro
2025-09-12 22:22   ` Linus Torvalds
2025-10-13  8:53     ` Jiri Slaby
2025-09-15  8:16   ` Uwe Kleine-König
2025-09-15 16:22     ` Sean Christopherson

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=aMBHfv3dQPZ0iLSM@google.com \
    --to=briannorris@chromium.org \
    --cc=davidgow@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®