| /Linux-v4.19/tools/perf/tests/ |
| D | bp_signal_overflow.c | 66 int fd, i, fails = 0; in test__bp_signal_overflow() local
124 fails++; in test__bp_signal_overflow()
130 fails++; in test__bp_signal_overflow()
133 return fails ? TEST_FAIL : TEST_OK; in test__bp_signal_overflow()
|
| /Linux-v4.19/tools/testing/selftests/bpf/ |
| D | test_sock.c | 439 int fails = 0; in run_tests() local
444 ++fails; in run_tests()
448 printf("Summary: %d PASSED, %d FAILED\n", passes, fails); in run_tests()
449 return fails ? -1 : 0; in run_tests()
|
| D | test_sock_addr.c | 1349 int fails = 0; in run_tests() local
1354 ++fails; in run_tests()
1358 printf("Summary: %d PASSED, %d FAILED\n", passes, fails); in run_tests()
1359 return fails ? -1 : 0; in run_tests()
|
| /Linux-v4.19/tools/testing/selftests/timers/ |
| D | freq-step.c | 249 int i, j, fails = 0; in main() local
261 fails += run_test(0, freq_base, freq_step); in main()
267 if (fails) in main()
|
| /Linux-v4.19/Documentation/power/ |
| D | basic-pm-debugging.txt | 18 systems might be necessary to make hibernation work. Thus, if your machine fails
41 To find out why hibernation fails on your system, you can use a special testing
95 without creating a hibernation image. Obviously, if the "devices" test fails,
101 If the "freezer" test fails, there is a task that cannot be frozen (in that case
107 If the "devices" test fails, most likely there is a driver that cannot suspend
111 - if the test fails, unload a half of the drivers currently loaded and repeat
127 If the "platform" test fails, there is a problem with the handling of the
132 If the "processors" test fails, the disabling/enabling of nonboot CPUs does not
138 If the "core" test fails, which means that suspending of the system/platform
158 - if there are n modules loaded and the attempt to suspend and resume fails,
|
| /Linux-v4.19/Documentation/cpu-freq/ |
| D | amd-powernow.txt | 34 and fall back to PST if that fails.
36 fall back to ACPI if the PSB support fails. A module parameter,
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-class-fpga-manager | 15 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
|
| D | sysfs-class-rc | 33 Write fails with EINVAL if an invalid protocol combination or
79 Write fails with EINVAL if an invalid protocol combination or
|
| /Linux-v4.19/Documentation/filesystems/ext4/ondisk/ |
| D | mmp.rst | 12 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-v4.19/arch/xtensa/include/asm/ |
| D | asm-uaccess.h | 91 # error Assembly macro kernel_ok fails
|
| /Linux-v4.19/Documentation/ |
| D | pi-futex.txt | 90 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-v4.19/Documentation/media/uapi/dvb/ |
| D | fe-get-event.rst | 39 or non-blocking mode. In the latter case, the call fails immediately
|
| D | dmx-fread.rst | 45 data that fails on CRC check will be silently ignored.
|
| D | video-get-event.rst | 58 in blocking or non-blocking mode. In the latter case, the call fails
|
| /Linux-v4.19/Documentation/media/uapi/v4l/ |
| D | func-poll.rst | 71 capturing. When that fails it returns a ``POLLERR`` as above. Otherwise
78 streaming. When that fails it returns a ``POLLERR`` as above. Otherwise
|
| D | func-ioctl.rst | 61 When an ioctl that takes an output or read/write parameter fails, the
|
| D | vidioc-querystd.rst | 44 will return V4L2_STD_UNKNOWN. When detection is not possible or fails,
|
| /Linux-v4.19/Documentation/media/uapi/rc/ |
| D | rc-sysfs-nodes.rst | 52 Write fails with ``EINVAL`` if an invalid protocol combination or unknown
110 Write fails with ``EINVAL`` if an invalid protocol combination or unknown
|
| /Linux-v4.19/Documentation/media/uapi/mediactl/ |
| D | media-func-ioctl.rst | 66 When an ioctl that takes an output or read/write parameter fails, the
|
| /Linux-v4.19/Documentation/media/uapi/cec/ |
| D | cec-func-ioctl.rst | 65 When an ioctl that takes an output or read/write parameter fails, the
|
| /Linux-v4.19/Documentation/thermal/ |
| D | exynos_thermal_emulation | 28 mode at the same time. (Or you have to keep the mode enabling.) If you don't, it fails to
|
| /Linux-v4.19/Documentation/hwmon/ |
| D | sht15 | 49 * If a CRC validation fails, a soft reset command is sent, which resets
|
| /Linux-v4.19/Documentation/vm/ |
| D | transhuge.rst | 18 - if a hugepage allocation fails because of memory fragmentation,
160 additional pins (i.e. from get_user_pages). split_huge_page() fails any
180 pmd can be split at any point and never fails.
|
| /Linux-v4.19/Documentation/devicetree/bindings/mfd/ |
| D | tps6507x.txt | 18 fails.
|
| /Linux-v4.19/Documentation/dev-tools/ |
| D | ubsan.rst | 8 that may cause UB. If check fails (i.e. UB detected) __ubsan_handle_*
|
