Home
last modified time | relevance | path

Searched refs:fails (Results 1 – 25 of 210) sorted by relevance

123456789

/Linux-v5.4/tools/perf/tests/
Dbp_signal_overflow.c67 int fd, i, fails = 0; in test__bp_signal_overflow() local
125 fails++; in test__bp_signal_overflow()
131 fails++; in test__bp_signal_overflow()
134 return fails ? TEST_FAIL : TEST_OK; in test__bp_signal_overflow()
/Linux-v5.4/tools/testing/selftests/bpf/
Dtest_section_names.c217 int fails = 0; in run_tests() local
222 ++fails; in run_tests()
226 printf("Summary: %d PASSED, %d FAILED\n", passes, fails); in run_tests()
227 return fails ? -1 : 0; in run_tests()
Dtest_sock.c449 int fails = 0; in run_tests() local
454 ++fails; in run_tests()
458 printf("Summary: %d PASSED, %d FAILED\n", passes, fails); in run_tests()
459 return fails ? -1 : 0; in run_tests()
/Linux-v5.4/tools/testing/selftests/bpf/prog_tests/
Dcore_reloc.c28 .fails = true, \
51 .fails = true, \
81 .fails = true, \
107 .fails = true, \
174 .fails = true, \
185 bool fails; member
324 if (test_case->fails) { in test_core_reloc()
Dbpf_verif_scale.c37 bool fails; member
106 CHECK_FAIL(err && !test->fails); in test_bpf_verif_scale()
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-platform-dfl-fme54 fails with -EINVAL if input parsing fails or input error code
63 fails with -EINVAL if input parsing fails or input error code
83 file to inject errors for testing purpose. Write fails with
84 -EINVAL if input parsing fails or input inject error code isn't
93 fials with -EINVAL if input parsing fails or input error code
Dsysfs-platform-dfl-port84 to clear errors. Write fails with -EINVAL if input parsing
85 fails or input error code doesn't match. Write fails with
Dsysfs-class-fpga-manager15 fails, that could be due to not being able to find the firmware
44 If FPGA programming operation fails, it could be caused by crc
Dsysfs-class-rc33 Write fails with EINVAL if an invalid protocol combination or
79 Write fails with EINVAL if an invalid protocol combination or
/Linux-v5.4/tools/testing/selftests/timers/
Dfreq-step.c241 int i, j, fails = 0; in main() local
253 fails += run_test(0, freq_base, freq_step); in main()
259 if (fails) in main()
/Linux-v5.4/Documentation/power/
Dbasic-pm-debugging.rst23 fails to hibernate or resume in the "reboot" mode, you should try the
47 To find out why hibernation fails on your system, you can use a special testing
103 without creating a hibernation image. Obviously, if the "devices" test fails,
109 If the "freezer" test fails, there is a task that cannot be frozen (in that case
115 If the "devices" test fails, most likely there is a driver that cannot suspend
120 - if the test fails, unload a half of the drivers currently loaded and repeat
136 If the "platform" test fails, there is a problem with the handling of the
141 If the "processors" test fails, the disabling/enabling of nonboot CPUs does not
147 If the "core" test fails, which means that suspending of the system/platform
168 - if there are n modules loaded and the attempt to suspend and resume fails,
/Linux-v5.4/Documentation/cpu-freq/
Damd-powernow.txt34 and fall back to PST if that fails.
36 fall back to ACPI if the PSB support fails. A module parameter,
/Linux-v5.4/Documentation/filesystems/ext4/
Dmmp.rst12 fsck is (hopefully) running, and open fails immediately. Otherwise, the
15 filesystem is active on another machine and the open fails. If the MMP
/Linux-v5.4/arch/xtensa/include/asm/
Dasm-uaccess.h89 # error Assembly macro kernel_ok fails
/Linux-v5.4/Documentation/
Dpi-futex.txt90 If the lock-acquire fastpath fails, [i.e. an atomic transition from 0 to
91 TID fails], then FUTEX_LOCK_PI is called. The kernel does all the
108 If the unlock fastpath fails (because the FUTEX_WAITERS bit is set),
/Linux-v5.4/fs/afs/
DKconfig37 the dmesg log if the server rotation algorithm fails to successfully
/Linux-v5.4/Documentation/core-api/
Dboot-time-mm.rst19 when an allocation fails and those that don't.
Dmemory-hotplug.rst20 Generated if MEM_GOING_ONLINE fails.
33 Generated if MEM_GOING_OFFLINE fails. Memory is available again from
/Linux-v5.4/Documentation/media/uapi/rc/
Drc-sysfs-nodes.rst59 Write fails with ``EINVAL`` if an invalid protocol combination or unknown
117 Write fails with ``EINVAL`` if an invalid protocol combination or unknown
/Linux-v5.4/Documentation/media/uapi/v4l/
Dfunc-poll.rst78 capturing. When that fails it returns a ``POLLERR`` as above. Otherwise
85 streaming. When that fails it returns a ``POLLERR`` as above. Otherwise
/Linux-v5.4/Documentation/media/uapi/dvb/
Dfe-get-event.rst46 or non-blocking mode. In the latter case, the call fails immediately
Ddmx-fread.rst52 data that fails on CRC check will be silently ignored.
/Linux-v5.4/Documentation/driver-api/thermal/
Dexynos_thermal_emulation.rst34 time. (Or you have to keep the mode enabling.) If you don't, it fails to
/Linux-v5.4/Documentation/media/uapi/mediactl/
Dmedia-func-ioctl.rst73 When an ioctl that takes an output or read/write parameter fails, the
/Linux-v5.4/Documentation/media/uapi/cec/
Dcec-func-ioctl.rst72 When an ioctl that takes an output or read/write parameter fails, the

123456789