Home
last modified time | relevance | path

Searched refs:succeeded (Results 1 – 25 of 39) sorted by relevance

12

/Linux-v4.19/include/trace/events/
Dmigrate.h48 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/
Dbreakpoint_test_arm64.c211 bool succeeded = true; in main() local
235 succeeded = false; in main()
250 succeeded = false; in main()
254 if (succeeded) in main()
Dstep_after_suspend_test.c175 bool succeeded = true; in main() local
212 succeeded = false; in main()
216 if (succeeded) in main()
/Linux-v4.19/Documentation/
Dnumastat.txt11 and succeeded.
24 and succeeded.
DDMA-API.txt68 allocation attempt succeeded.
122 allocation attempt succeeded.
/Linux-v4.19/sound/pci/oxygen/
Doxygen_io.c132 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/
Drport_state_diagram.dot15 … -> running [ label = "fast_io_fail_tmo = off and\ndev_loss_tmo = off;\nreconnecting succeeded" ];
/Linux-v4.19/Documentation/media/uapi/dvb/
Dca-fopen.rst55 When an ``open()`` call has succeeded, the device will be ready for use. The
Daudio-fopen.rst69 succeeded, the device will be ready for use. The significance of
Dvideo-fopen.rst69 When an open() call has succeeded, the device will be ready for use. The
Dfrontend_f_open.rst68 When an open() call has succeeded, the device will be ready for use in
/Linux-v4.19/tools/testing/selftests/ftrace/
DREADME52 * PASS: The test succeeded as expected. The test which exits with 0 is
/Linux-v4.19/Documentation/driver-api/pm/
Dnotifiers.rst58 ``PM_SUSPEND_PREPARE`` event, the notifiers that have already succeeded for that
/Linux-v4.19/Documentation/powerpc/
Dsyscall64-abi.txt23 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/
DAddingTestCases.txt54 verifyCmd to prove the command under test succeeded. This pattern
/Linux-v4.19/Documentation/sound/designs/
Dseq-oss.rst266 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/
Dcgroups.txt561 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/
Doracle-dax.txt360 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/
Dcoding-style.rst890 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/
Dfallback-mechanisms.rst97 succeeded.
/Linux-v4.19/net/ipv4/
Dfib_trie.c1240 goto succeeded; in fib_table_insert()
1289 succeeded: in fib_table_insert()
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-power206 succeeded, the work item requeues itself until user space
/Linux-v4.19/Documentation/serial/
Ddriver419 registered using uart_add_one_port after this call has succeeded.
/Linux-v4.19/Documentation/media/kapi/
Dcec-core.rst85 clean up. But if cec_register_adapter() succeeded, then only call
/Linux-v4.19/Documentation/filesystems/caching/
Dfscache.txt231 ok=N Number of acq reqs succeeded

12