mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 6.14-rc4
Date: Mon, 24 Feb 2025 18:21:40 -0800	[thread overview]
Message-ID: <035ff595-8277-4680-a64e-a1bd8c141e04@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wi9Aa_sgCjSncJ7odZX_f=v5WZwWm+GuwXmVy1O+wiBsw@mail.gmail.com>

On Sun, Feb 23, 2025 at 12:49:22PM -0800, Linus Torvalds wrote:
> This continues to be the right kind of "boring" release: nothing in
> particular stands out in rc4.
> 
> We've got all the usual driver fixes (ok, let networking than usual,
> but gpu, sound, nvme, you name it, but it won't be huge), various
> smaller filesystem fixes (xfs, smb, netfs, cachefs), core kernel and
> networking fixes.
> 
> And all of it looks pretty small and non-threatening. The biggest
> single patch is just a new self test.
> 
> So - knock wood - 6.14 looks to be on track, with everything looking good.
> 
> Please keep testing,
> 

Time for a report.

Build results:
	total: 161 pass: 161 fail: 0
Qemu test results:
	total: 619 pass: 619 fail: 0
Unit test results:
	pass: 565894 fail: 0

I recently enabled boot tests with PREEMPT_RT enabled. This triggers some
tracebacks in older network drivers. Nothing special, though, so I won't
provide details here. For those interested, preliminary fixes for two of
the problems are available in my 'fixes' branch at
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git.

b364dd4ed219 possible circular locking dependency backtrace seen when enabling PREEMPT_RT
8571385b8fbf lockdep: Don't disable interrupts on RT in disable_irq_nosync_lockdep.*()

Guenter

  reply	other threads:[~2025-02-25  2:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-23 20:49 Linus Torvalds
2025-02-25  2:21 ` Guenter Roeck [this message]
2025-02-26 22:28 ` Frank Scheiner

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=035ff595-8277-4680-a64e-a1bd8c141e04@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-kernel@vger.kernel.org \
    --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®