/Linux-v4.19/include/trace/events/ |
D | migrate.h | 48 TP_PROTO(unsigned long succeeded, unsigned long failed, 51 TP_ARGS(succeeded, failed, mode, reason), 54 __field( unsigned long, succeeded) 61 __entry->succeeded = succeeded; 68 __entry->succeeded,
|
/Linux-v4.19/tools/testing/selftests/breakpoints/ |
D | breakpoint_test_arm64.c | 211 bool succeeded = true; in main() local 235 succeeded = false; in main() 250 succeeded = false; in main() 254 if (succeeded) in main()
|
D | step_after_suspend_test.c | 175 bool succeeded = true; in main() local 212 succeeded = false; in main() 216 if (succeeded) in main()
|
/Linux-v4.19/Documentation/ |
D | numastat.txt | 11 and succeeded. 24 and succeeded.
|
D | DMA-API.txt | 68 allocation attempt succeeded. 122 allocation attempt succeeded.
|
/Linux-v4.19/sound/pci/oxygen/ |
D | oxygen_io.c | 132 unsigned int count, succeeded; in oxygen_write_ac97() local 139 succeeded = 0; in oxygen_write_ac97() 145 ++succeeded >= 2) { in oxygen_write_ac97()
|
/Linux-v4.19/Documentation/scsi/scsi_transport_srp/ |
D | rport_state_diagram.dot | 15 … -> running [ label = "fast_io_fail_tmo = off and\ndev_loss_tmo = off;\nreconnecting succeeded" ];
|
/Linux-v4.19/Documentation/media/uapi/dvb/ |
D | ca-fopen.rst | 55 When an ``open()`` call has succeeded, the device will be ready for use. The
|
D | audio-fopen.rst | 69 succeeded, the device will be ready for use. The significance of
|
D | video-fopen.rst | 69 When an open() call has succeeded, the device will be ready for use. The
|
D | frontend_f_open.rst | 68 When an open() call has succeeded, the device will be ready for use in
|
/Linux-v4.19/tools/testing/selftests/ftrace/ |
D | README | 52 * PASS: The test succeeded as expected. The test which exits with 0 is
|
/Linux-v4.19/Documentation/driver-api/pm/ |
D | notifiers.rst | 58 ``PM_SUSPEND_PREPARE`` event, the notifiers that have already succeeded for that
|
/Linux-v4.19/Documentation/powerpc/ |
D | syscall64-abi.txt | 23 the syscall succeeded and r3 is the return value. When cr0.SO is set, the
|
/Linux-v4.19/tools/testing/selftests/tc-testing/creating-testcases/ |
D | AddingTestCases.txt | 54 verifyCmd to prove the command under test succeeded. This pattern
|
/Linux-v4.19/Documentation/sound/designs/ |
D | seq-oss.rst | 266 normal MIDI devices. If the open procedure succeeded, return zero. Otherwise, 292 if succeeded, and -errno if failed. The format argument is the patch key
|
/Linux-v4.19/Documentation/cgroup-v1/ |
D | cgroups.txt | 561 has succeeded on @cgrp. This signifies the beginning of the end of 614 Called when a task attach operation has failed after can_attach() has succeeded. 618 succeeded. The parameters are identical to can_attach(). 672 able to tell whether a command succeeded or failed.
|
/Linux-v4.19/Documentation/sparc/oradax/ |
D | oracle-dax.txt | 360 if (completion_area[0] != 1) { /* section 36.2.2, 1 = command ran and succeeded */ 423 if (completion_area[0] != 1) { /* section 36.2.2, 1 = command ran and succeeded */
|
/Linux-v4.19/Documentation/process/ |
D | coding-style.rst | 890 most common is a value indicating whether the function succeeded or 892 (-Exxx = failure, 0 = success) or a ``succeeded`` boolean (0 = failure, 903 is a predicate, the function should return a "succeeded" boolean. 915 than an indication of whether the computation succeeded, are not subject to
|
/Linux-v4.19/Documentation/driver-api/firmware/ |
D | fallback-mechanisms.rst | 97 succeeded.
|
/Linux-v4.19/net/ipv4/ |
D | fib_trie.c | 1240 goto succeeded; in fib_table_insert() 1289 succeeded: in fib_table_insert()
|
/Linux-v4.19/Documentation/ABI/testing/ |
D | sysfs-power | 206 succeeded, the work item requeues itself until user space
|
/Linux-v4.19/Documentation/serial/ |
D | driver | 419 registered using uart_add_one_port after this call has succeeded.
|
/Linux-v4.19/Documentation/media/kapi/ |
D | cec-core.rst | 85 clean up. But if cec_register_adapter() succeeded, then only call
|
/Linux-v4.19/Documentation/filesystems/caching/ |
D | fscache.txt | 231 ok=N Number of acq reqs succeeded
|