lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4776411.vXUDI8C0e8@n9w6sw14>
Date: Thu, 9 Jan 2025 12:27:16 +0100
From: Christian Eggers <ceggers@...i.de>
To: <linux-rt-users@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Subject: Re: [RT] v6.12-rt stable branch?

On Thursday, 9 January 2025, 11:47:57 CET, Sebastian Andrzej Siewior wrote:
> On 2025-01-09 09:35:20 [+0100], Alexander Dahl wrote:
> > Hei hei,
> > 
> > Am Thu, Jan 09, 2025 at 09:23:23AM +0100 schrieb Christian Eggers:
> > > Although most of the remaining RT stuff has been merged into linux-6.12, there
> > > seems to be still no out-of-the box support for RT on ARM 32 bit platforms.
> > 
> > This is also how I understood it.
> 
> I've been asking who needs ARM support and nobody spoke up. Arnd then
> picked up some of the patches and for v6.13 the ARM queue got smaller.
> 
> Looking at what affects ARM from the queue there is just the ktimer
> thread and the ARM specific bits. Lazy-preempt isn't implemented.
> 
> > > Are there any plans to release (and maintain) a v6.12-rt stable branch? Or shall
> > > I pickup the necessary patches into my local branch myself?
> > 
> > We have some systems with Microchip AT91 SoCs (SAMA5D2, SAM9X60) and I
> > would be interested in those patches as well.  The last patch
> > published was 6.12-rc4-rt6 from october.
> 
> v6.12 is a LTS. And I wanted to add some PowerPC bits because it does
> not boot on some parts as I've been told.
> What about I make a release for the current stable tree and then update
> it once the patches no longer apply on a newer stable tree?

For me this would be fine.

> 
> > Greets
> > Alex
> 
> Sebastian
> 

Thanks,
Christian




Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ