21 May
2025
21 May
'25
6:49 p.m.
On Wed, May 21, 2025 at 03:45:42PM +0200, Thomas Weißschuh wrote:
Or you could run your testsuite with the new nolibc for-next branch which should be fixed now.
That seems to build with 869c788909b93a78ead1ca28c42b95eeb0779215 which is the current HEAD of:
git://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git for-next