On Fri, May 23, 2025 at 10:33:13AM +0200, Thomas Weißschuh wrote:
> On 2025-05-21 19:49:39+0100, Mark Brown wrote:

> > 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

> Thanks for testing!

> To be sure, was this your full test-run? Or did you do a full test-run

Just a build of the arm64 selftests (which are the only thing I build
that was affected).

> on linux-next in the meantime?
> I'd like to get your confirmation before sending these changes to Linus.

Today's -next appears to have built and be running the arm64 selftests
OK again in my personal CI:

   https://lava.sirena.org.uk/scheduler/job/1419721#L2482

There shoud also be results (both build and runtime) from KernelCI:

   https://dashboard.kernelci.org/

but there might be a bit more lag seeing the results there.

Attachment: signature.asc
Description: PGP signature

Reply via email to