Home
last modified time | relevance | path

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

12345678910

/Linux-v5.10/tools/testing/selftests/bpf/prog_tests/
Dcore_extern.c26 bool fails; member
59 { .name = "tristate (int)", .fails = 1, .cfg = CFG"CONFIG_TRISTATE=1" },
60 { .name = "tristate (bad)", .fails = 1, .cfg = CFG"CONFIG_TRISTATE=M" },
66 { .name = "bool (tristate)", .fails = 1, .cfg = CFG"CONFIG_BOOL=m" },
67 { .name = "bool (int)", .fails = 1, .cfg = CFG"CONFIG_BOOL=1" },
71 { .name = "char (bad)", .fails = 1, .cfg = CFG"CONFIG_CHAR=q\n" },
72 { .name = "char (empty)", .fails = 1, .cfg = CFG"CONFIG_CHAR=\n" },
73 { .name = "char (str)", .fails = 1, .cfg = CFG"CONFIG_CHAR=\"y\"\n" },
81 { .name = "str (no value)", .fails = 1, .cfg = CFG"CONFIG_STR=\n" },
82 { .name = "str (bad value)", .fails = 1, .cfg = CFG"CONFIG_STR=bla\n" },
[all …]
Dcore_reloc.c33 .fails = true, \
56 .fails = true, \
87 .fails = true, \
113 .fails = true, \
180 .fails = true, \
190 .fails = true, \
221 .fails = true, \
226 .fails = true, \
255 .fails = true, \
272 .fails = true, \
[all …]
Dcpu_mask.c35 bool fails; member
66 if (test_cases[i].fails) { in test_cpu_mask()
Dbpf_verif_scale.c39 bool fails; member
114 CHECK_FAIL(err && !test->fails); in test_bpf_verif_scale()
/Linux-v5.10/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.10/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
197 clamped within the range from 0 to 127 Watts. Write fails with
198 -EINVAL if input parsing fails.
210 clamped within the range from 0 to 127 Watts. Write fails with
211 -EINVAL if input parsing fails.
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
43 If FPGA programming operation fails, it could be caused by crc
/Linux-v5.10/tools/testing/selftests/bpf/
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.10/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.10/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.10/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.10/arch/xtensa/include/asm/
Dasm-uaccess.h89 # error Assembly macro kernel_ok fails
/Linux-v5.10/drivers/of/unittest-data/
Doverlay_bad_add_dup_prop.dts19 * fails, the memory leak does actually occur, and kmemleak will
/Linux-v5.10/Documentation/locking/
Dpi-futex.rst90 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.10/Documentation/userspace-api/media/dvb/
Dfe-get-event.rst38 or non-blocking mode. In the latter case, the call fails immediately
/Linux-v5.10/fs/afs/
DKconfig37 the dmesg log if the server rotation algorithm fails to successfully
/Linux-v5.10/Documentation/userspace-api/media/rc/
Drc-sysfs-nodes.rst52 Write fails with ``EINVAL`` if an invalid protocol combination or unknown
110 Write fails with ``EINVAL`` if an invalid protocol combination or unknown
/Linux-v5.10/Documentation/userspace-api/media/v4l/
Dfunc-poll.rst68 capturing. When that fails it returns a ``POLLERR`` as above. Otherwise
75 streaming. When that fails it returns a ``POLLERR`` as above. Otherwise
Dfunc-ioctl.rst57 When an ioctl that takes an output or read/write parameter fails, the
/Linux-v5.10/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.10/Documentation/userspace-api/media/cec/
Dcec-func-ioctl.rst62 When an ioctl that takes an output or read/write parameter fails, the
/Linux-v5.10/Documentation/userspace-api/media/mediactl/
Dmedia-func-ioctl.rst62 When an ioctl that takes an output or read/write parameter fails, the
Drequest-func-ioctl.rst62 When an ioctl that takes an output or read/write parameter fails, the

12345678910