On 2023-06-27 15:14:35 [-0400], Joseph Salisbury wrote:
> Hi Sebastian,
Hi Joseph,
> Thanks for the heads up on these commits!
>
> It appears v5.15 will need these commits:
>
> d15121be7485 ("revert: "softirq: Let ksoftirqd do its job"")
> 2951580ba6ad ("tracing/timer: Add missing hrtimer modes to
> decode_hrtimer_mode().")
> 7eb16f23b9a41 ("io-mapping: don't disable preempt on RT in
> io_mapping_map_atomic_wc().")
> 286deb7ec03d9 ("locking/rwbase: Mitigate indefinite writer starvation")
>
> The following commit was already added to v5.15 in v5.15.109:
>
> c15737965434 (rtmutex: Add acquire semantics for rtmutex lock acquisition
> slow path)
>
>
> The latest two commits are still in linux-next and have not landed in
> mainline as of yet (d15121be7485 and 2951580ba6ad). Should I wait to add
> them to the v5.15-rt stable tree and see if Greg adds them to his trees
> first?
They should end up mainline during this merge window. You can wait until
-rc1/-rc2 if you want. If they end-up in the stable-tree, they should
easily vanish from your RT-queue.
Either way, please wait until until they show up in v6.1-RT so patches
flow from the youngest kernel to the oldest.
> Thanks,
>
> Joe
Sebastian
