Searched refs:succeeded (Results 1 – 22 of 22) sorted by relevance
| /linux-4.4.14/include/trace/events/ |
| D | migrate.h | 47 TP_PROTO(unsigned long succeeded, unsigned long failed,
50 TP_ARGS(succeeded, failed, mode, reason),
53 __field( unsigned long, succeeded)
60 __entry->succeeded = succeeded;
67 __entry->succeeded,
|
| /linux-4.4.14/Documentation/ |
| D | numastat.txt | 9 and succeeded.
22 and succeeded.
|
| D | CodingStyle | 777 most common is a value indicating whether the function succeeded or
779 (-Exxx = failure, 0 = success) or a "succeeded" boolean (0 = failure,
790 is a predicate, the function should return a "succeeded" boolean.
802 than an indication of whether the computation succeeded, are not subject to
|
| D | DMA-API.txt | 63 allocation attempt succeeded.
111 allocation attempt succeeded.
|
| D | applying-patches.txt | 142 If you get "Hunk #2 succeeded at 1887 with fuzz 2 (offset 7 lines)." or a
|
| /linux-4.4.14/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-4.4.14/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-4.4.14/tools/testing/selftests/ftrace/ |
| D | README | 52 * PASS: The test succeeded as expected. The test which exits with 0 is
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | cgroups.txt | 566 has succeeded on @cgrp. This signifies the beginning of the end of
619 Called when a task attach operation has failed after can_attach() has succeeded.
623 succeeded. The parameters are identical to can_attach().
677 able to tell whether a command succeeded or failed.
|
| D | cpusets.txt | 830 able to tell whether a command succeeded or failed.
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-power | 199 succeeded, the work item requeues itself until user space
|
| /linux-4.4.14/net/ipv4/ |
| D | fib_trie.c | 1198 goto succeeded; in fib_table_insert()
1248 succeeded: in fib_table_insert()
|
| /linux-4.4.14/Documentation/serial/ |
| D | driver | 402 registered using uart_add_one_port after this call has succeeded.
|
| /linux-4.4.14/Documentation/scsi/ |
| D | scsi_eh.txt | 334 handler returns SUCCESS if it has succeeded to make LLDD and
|
| D | ChangeLog.lpfc | 478 succeeded.
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | fscache.txt | 231 ok=N Number of acq reqs succeeded
|
| /linux-4.4.14/Documentation/vm/ |
| D | frontswap.txt | 58 succ_stores - how many store attempts have succeeded
|
| /linux-4.4.14/Documentation/timers/ |
| D | NO_HZ.txt | 245 whether or not you have succeeded in removing OS jitter from your system.
|
| /linux-4.4.14/Documentation/trace/ |
| D | ring-buffer-design.txt | 911 will see it succeeded in updating the pointer from NORMAL to HEAD.
|
| /linux-4.4.14/Documentation/RCU/ |
| D | trace.txt | 258 new expedited grace period succeeded.
|
| /linux-4.4.14/Documentation/locking/ |
| D | rt-mutex-design.txt | 345 if the variable is what you expect it to be. You know if it succeeded if
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | CHANGES | 1045 … eventual trap when mounting twice to different shares on the same server when the first succeeded
|