Thomas Weißschuh 00ddf4cc97 selftests/nolibc: only run constructor tests on nolibc ... The nolibc testsuite can be run against other libcs to test for interoperability. Some aspects of the constructor execution are not standardized and musl does not provide all tested feature, for one it does not provide arguments to the constructors, anymore? Skip the constructor tests on non-nolibc configurations. Acked-by: Willy Tarreau <w@1wt.eu> Link: https://lore.kernel.org/r/20250212-nolibc-test-constructor-v1-1-c963875b3da4@weissschuh.net Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>		2025-02-20 22:04:12 +01:00
..
crypto/chacha20-s390
cxl	cxl changes for v6.14	2025-01-29 11:23:22 -08:00
fault-injection
ktest	ktest.pl: Fix typo "accesing"	2024-12-18 16:51:50 -05:00
kunit	The various patchsets are summarized below. Plus of course many	2025-01-26 18:36:23 -08:00
memblock	memblock: updates for 6.12-rc1	2024-09-25 11:35:19 -07:00
nvdimm	Get rid of 'remove_new' relic from platform driver struct	2024-12-01 15:12:43 -08:00
radix-tree	Xarray: do not return sibling entries from xas_find_marked()	2025-01-24 22:47:27 -08:00
scatterlist
selftests	selftests/nolibc: only run constructor tests on nolibc	2025-02-20 22:04:12 +01:00
shared	tools: fix atomic_set() definition to set the value correctly	2025-01-12 19:03:35 -08:00
vma	tools: add VM_WARN_ON_VMG definition	2025-01-25 20:22:46 -08:00
vsock	vsock/test: Add test for connect() retries	2025-01-29 18:50:37 -08:00