Home
last modified time | relevance | path

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

12

/Linux-v5.4/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-v5.4/tools/testing/selftests/breakpoints/
Dbreakpoint_test_arm64.c202 bool succeeded = true; in main() local
227 succeeded = false; in main()
242 succeeded = false; in main()
246 if (succeeded) in main()
Dstep_after_suspend_test.c166 bool succeeded = true; in main() local
211 succeeded = false; in main()
215 if (succeeded) in main()
/Linux-v5.4/Documentation/admin-guide/
Dnumastat.rst11 and succeeded.
24 and succeeded.
/Linux-v5.4/sound/pci/oxygen/
Doxygen_io.c120 unsigned int count, succeeded; in oxygen_write_ac97() local
127 succeeded = 0; in oxygen_write_ac97()
133 ++succeeded >= 2) { in oxygen_write_ac97()
/Linux-v5.4/Documentation/scsi/scsi_transport_srp/
Drport_state_diagram.dot15 … -> running [ label = "fast_io_fail_tmo = off and\ndev_loss_tmo = off;\nreconnecting succeeded" ];
/Linux-v5.4/Documentation/media/uapi/dvb/
Dca-fopen.rst62 When an ``open()`` call has succeeded, the device will be ready for use. The
Daudio-fopen.rst76 succeeded, the device will be ready for use. The significance of
Dvideo-fopen.rst76 When an open() call has succeeded, the device will be ready for use. The
Dfrontend_f_open.rst75 When an open() call has succeeded, the device will be ready for use in
/Linux-v5.4/tools/testing/selftests/ftrace/
DREADME52 * PASS: The test succeeded as expected. The test which exits with 0 is
/Linux-v5.4/Documentation/driver-api/pm/
Dnotifiers.rst62 ``PM_SUSPEND_PREPARE`` event, the notifiers that have already succeeded for that
/Linux-v5.4/Documentation/powerpc/
Dsyscall64-abi.rst23 the syscall succeeded and r3 is the return value. When cr0.SO is set, the
/Linux-v5.4/tools/testing/selftests/tc-testing/creating-testcases/
DAddingTestCases.txt59 verifyCmd to prove the command under test succeeded. This pattern
/Linux-v5.4/Documentation/networking/
Dsnmp_counter.rst1088 Connection to 192.168.122.251 9000 port [tcp/*] succeeded!
1130 Connection to nstat-b 9000 port [tcp/*] succeeded!
1135 Connection to nstat-b 9000 port [tcp/*] succeeded!
1169 Connection to nstat-b 9000 port [tcp/*] succeeded!
1514 Connection to nstat-b 9000 port [tcp/*] succeeded!
1530 won't see the "Connection to ... succeeded!" string, because kernel
1532 on an old kernel, you would see that the connection is succeeded,
1712 Connection to nstat-b 9000 port [tcp/*] succeeded!
1755 Connection to nstat-b 9000 port [tcp/*] succeeded!
1758 Connection to nstat-b 9001 port [tcp/*] succeeded!
/Linux-v5.4/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-v5.4/Documentation/admin-guide/cgroup-v1/
Dcgroups.rst577 has succeeded on @cgrp. This signifies the beginning of the end of
630 Called when a task attach operation has failed after can_attach() has succeeded.
634 succeeded. The parameters are identical to can_attach().
691 able to tell whether a command succeeded or failed.
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-power206 succeeded, the work item requeues itself until user space
317 of times entering system sleep state succeeded.
/Linux-v5.4/Documentation/sparc/oradax/
Doracle-dax.rst367 if (completion_area[0] != 1) { /* section 36.2.2, 1 = command ran and succeeded */
433 if (completion_area[0] != 1) { /* section 36.2.2, 1 = command ran and succeeded */
/Linux-v5.4/Documentation/process/
Dcoding-style.rst914 most common is a value indicating whether the function succeeded or
916 (-Exxx = failure, 0 = success) or a ``succeeded`` boolean (0 = failure,
927 is a predicate, the function should return a "succeeded" boolean.
939 than an indication of whether the computation succeeded, are not subject to
/Linux-v5.4/Documentation/driver-api/firmware/
Dfallback-mechanisms.rst97 succeeded.
/Linux-v5.4/net/ipv4/
Dfib_trie.c1236 goto succeeded; in fib_table_insert()
1285 succeeded: in fib_table_insert()
/Linux-v5.4/Documentation/driver-api/serial/
Ddriver.rst480 registered using uart_add_one_port after this call has succeeded.
/Linux-v5.4/Documentation/vm/
Dfrontswap.rst70 how many store attempts have succeeded
/Linux-v5.4/Documentation/timers/
Dno_hz.rst222 whether or not you have succeeded in removing OS jitter from your system.

12