From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: LKML <linux-kernel@vger.kernel.org>,linux-rt-users
<linux-rt-users@vger.kernel.org>,Steven Rostedt
<rostedt@goodmis.org>,Thomas Gleixner
<tglx@linutronix.de>,Carsten Emde <C.Emde@osadl.org>,John Kacur
<jkacur@redhat.com>,Sebastian Andrzej Siewior
<bigeasy@linutronix.de>,Daniel Wagner
<daniel.wagner@suse.com>,Tom Zanussi
<tom.zanussi@linux.intel.com>,Clark Williams
<williams@redhat.com>,Pavel Machek <pavel@denx.de>,Joseph
Salisbury <joseph.salisbury@canonical.com>
Subject: [ANNOUNCE] 5.15.133-rt70
Date: Tue, 24 Oct 2023 18:56:13 -0000 [thread overview]
Message-ID: <169817377329.1028379.7397120764831029877@jupiter.home.arpa> (raw)
Hello RT-list!
I'm pleased to announce the 5.15.133-rt70 stable release.
Note that this is strictly changes to PREEMPT_RT behavior with the following
commits:
ea14d5391ab6 drm/i915: Do not disable preemption for resets
23b43390beed posix-timers: Ensure timer ID search-loop limit is valid
33390dbc8270 bpf: Remove in_atomic() from bpf_link_put().
83098c4ddc86 mm/page_alloc: Use write_seqlock_irqsave() instead write_seqlock() + local_irq_save().
08d5582b4fad locking/seqlock: Do the lockdep annotation before locking in do_write_seqcount_begin_nested()
2f43c8cdd66e sched: avoid false lockdep splat in put_task_struct()
087228e58a7f debugobjects,locking: Annotate debug_object_fill_pool() wait type violation
2139bd98f2d2 debugobject: Ensure pool refill (again)
953acf822668 Revert "softirq: Let ksoftirqd do its job"
108971fa0a8e locking/rwbase: Mitigate indefinite writer starvation
f2a15c7f3231 io-mapping: don't disable preempt on RT in io_mapping_map_atomic_wc().
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
branch: v5.15-rt
Head SHA1: 2c1b5deb5b48082f07576d177ebf458e3798e85e
Or to build 5.15.133-rt70 directly, the following patches should be applied:
https://www.kernel.org/pub/linux/kernel/v5.x/linux-5.15.tar.xz
https://www.kernel.org/pub/linux/kernel/v5.x/patch-5.15.133.xz
https://www.kernel.org/pub/linux/kernel/projects/rt/5.15/patch-5.15.133-rt70.patch.xz
Enjoy!
Joseph Salisbury
reply other threads:[~2023-10-24 19:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=169817377329.1028379.7397120764831029877@jupiter.home.arpa \
--to=joseph.salisbury@canonical.com \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=daniel.wagner@suse.com \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pavel@denx.de \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
--cc=williams@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).