| /linux/include/trace/events/ |
| H A D | migrate.h | 51 TP_PROTO(unsigned long succeeded, unsigned long failed,
56 TP_ARGS(succeeded, failed, thp_succeeded, thp_failed,
60 __field( unsigned long, succeeded)
71 __entry->succeeded = succeeded;
82 __entry->succeeded,
|
| /linux/tools/testing/selftests/breakpoints/ |
| H A D | breakpoint_test_arm64.c | 202 bool succeeded = true; in main() local
227 succeeded = false; in main()
242 succeeded = false; in main()
246 if (succeeded) in main()
|
| H A D | step_after_suspend_test.c | 190 bool succeeded = true; in main() local
240 succeeded = false; in main()
245 if (succeeded) in main()
|
| /linux/Documentation/admin-guide/ |
| H A D | numastat.rst | 12 the preferred node and numa_miss on the node where allocation succeeded.
26 and succeeded.
41 and succeeded.
|
| /linux/sound/pci/oxygen/ |
| H A D | oxygen_io.c | 120 unsigned int count, succeeded; in oxygen_write_ac97() local
127 succeeded = 0; in oxygen_write_ac97()
133 ++succeeded >= 2) { in oxygen_write_ac97()
|
| /linux/Documentation/scsi/scsi_transport_srp/ |
| H A D | rport_state_diagram.dot | 15 … -> running [ label = "fast_io_fail_tmo = off and\ndev_loss_tmo = off;\nreconnecting succeeded" ];
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | ca-fopen.rst | 52 When an ``open()`` call has succeeded, the device will be ready for use. The
|
| H A D | frontend_f_open.rst | 65 When an open() call has succeeded, the device will be ready for use in
|
| /linux/tools/testing/selftests/ftrace/ |
| H A D | README | 52 * PASS: The test succeeded as expected. The test which exits with 0 is
|
| /linux/Documentation/driver-api/pm/ |
| H A D | notifiers.rst | 62 ``PM_SUSPEND_PREPARE`` event, the notifiers that have already succeeded for that
|
| /linux/Documentation/core-api/ |
| H A D | netlink.rst | 34 commands. User only gets information whether the operation succeeded or
|
| /linux/Documentation/networking/ |
| H A D | snmp_counter.rst | 1084 Connection to 192.168.122.251 9000 port [tcp/*] succeeded!
1126 Connection to nstat-b 9000 port [tcp/*] succeeded!
1131 Connection to nstat-b 9000 port [tcp/*] succeeded!
1165 Connection to nstat-b 9000 port [tcp/*] succeeded!
1510 Connection to nstat-b 9000 port [tcp/*] succeeded!
1526 won't see the "Connection to ... succeeded!" string, because kernel
1528 on an old kernel, you would see that the connection is succeeded,
1708 Connection to nstat-b 9000 port [tcp/*] succeeded!
1751 Connection to nstat-b 9000 port [tcp/*] succeeded!
1754 Connection to nstat-b 9001 port [tcp/*] succeeded!
|
| /linux/tools/testing/selftests/tc-testing/creating-testcases/ |
| H A D | AddingTestCases.txt | 61 verifyCmd to prove the command under test succeeded. This pattern
|
| /linux/Documentation/arch/powerpc/ |
| H A D | syscall64-abi.rst | 34 clear, the syscall succeeded and r3 is the return value. When cr0.SO is set,
|
| /linux/Documentation/sound/designs/ |
| H A 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/Documentation/admin-guide/cgroup-v1/ |
| H A D | cgroups.rst | 579 has succeeded on @cgrp. This signifies the beginning of the end of
632 Called when a task attach operation has failed after can_attach() has succeeded.
636 succeeded. The parameters are identical to can_attach().
693 able to tell whether a command succeeded or failed.
|
| /linux/Documentation/arch/sparc/oradax/ |
| H A D | oracle-dax.rst | 367 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/Documentation/filesystems/caching/ |
| H A D | fscache.rst | 180 | |ok=N |Number of acq reqs succeeded |
|
| /linux/Documentation/process/ |
| H A D | coding-style.rst | 1009 most common is a value indicating whether the function succeeded or
1011 (-Exxx = failure, 0 = success) or a ``succeeded`` boolean (0 = failure,
1022 is a predicate, the function should return a "succeeded" boolean.
1034 than an indication of whether the computation succeeded, are not subject to
|
| /linux/scripts/ |
| H A D | spelling.txt | 1555 succeded||succeeded
1560 successed||succeeded
|
| /linux/Documentation/filesystems/iomap/ |
| H A D | operations.rst | 153 after the range is read in, regardless of whether the read succeeded or
364 completes for the range, regardless of whether the writeback succeeded or
|
| /linux/net/ipv4/ |
| H A D | fib_trie.c | 1318 goto succeeded; in fib_table_insert()
1382 succeeded: in fib_table_insert()
|
| /linux/Documentation/driver-api/firmware/ |
| H A D | fallback-mechanisms.rst | 98 succeeded.
|
| /linux/Documentation/filesystems/ |
| H A D | directory-locking.rst | 260 Since the operation has succeeded, neither source nor target could have
|
| /linux/Documentation/timers/ |
| H A D | no_hz.rst | 213 whether or not you have succeeded in removing OS jitter from your system.
|