Home
last modified time | relevance | path

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

123

/linux/include/trace/events/
A Dmigrate.h50 TP_PROTO(unsigned long succeeded, unsigned long failed,
54 TP_ARGS(succeeded, failed, thp_succeeded, thp_failed,
58 __field( unsigned long, succeeded)
68 __entry->succeeded = succeeded;
78 __entry->succeeded,
/linux/tools/testing/selftests/breakpoints/
A 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()
A Dstep_after_suspend_test.c167 bool succeeded = true; in main() local
217 succeeded = false; in main()
222 if (succeeded) in main()
/linux/Documentation/admin-guide/
A Dnumastat.rst12 the preferred node and numa_miss on the node where allocation succeeded.
26 and succeeded.
41 and succeeded.
/linux/sound/pci/oxygen/
A 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/Documentation/ABI/testing/
A Dsysfs-kernel-mm-cma19 the number of pages CMA API succeeded to allocate
A Dsysfs-power210 succeeded, the work item requeues itself until user space
322 of times entering system sleep state succeeded.
/linux/Documentation/scsi/scsi_transport_srp/
A Drport_state_diagram.dot15 … -> running [ label = "fast_io_fail_tmo = off and\ndev_loss_tmo = off;\nreconnecting succeeded" ];
/linux/Documentation/userspace-api/media/dvb/
A Dca-fopen.rst52 When an ``open()`` call has succeeded, the device will be ready for use. The
A Dfrontend_f_open.rst65 When an open() call has succeeded, the device will be ready for use in
/linux/drivers/staging/media/av7110/
A Daudio-fopen.rst66 succeeded, the device will be ready for use. The significance of
A Dvideo-fopen.rst67 When an open() call has succeeded, the device will be ready for use. The
/linux/tools/testing/selftests/ftrace/
A DREADME52 * PASS: The test succeeded as expected. The test which exits with 0 is
/linux/Documentation/driver-api/pm/
A Dnotifiers.rst62 ``PM_SUSPEND_PREPARE`` event, the notifiers that have already succeeded for that
/linux/Documentation/dev-tools/kunit/
A Dtips.rst42 /* Ensure allocation succeeded. */
/linux/Documentation/networking/
A 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/tools/testing/selftests/tc-testing/creating-testcases/
A DAddingTestCases.txt59 verifyCmd to prove the command under test succeeded. This pattern
/linux/Documentation/powerpc/
A Dsyscall64-abi.rst34 clear, the syscall succeeded and r3 is the return value. When cr0.SO is set,
/linux/Documentation/sound/designs/
A 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/Documentation/admin-guide/cgroup-v1/
A 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/Documentation/driver-api/media/
A Dcamera-sensor.rst151 The function returns a non-zero value if it succeeded getting the power count or
/linux/Documentation/sparc/oradax/
A 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/Documentation/process/
A Dcoding-style.rst990 most common is a value indicating whether the function succeeded or
992 (-Exxx = failure, 0 = success) or a ``succeeded`` boolean (0 = failure,
1003 is a predicate, the function should return a "succeeded" boolean.
1015 than an indication of whether the computation succeeded, are not subject to
/linux/scripts/
A Dspelling.txt1410 succeded||succeeded
1414 successed||succeeded
/linux/Documentation/gpu/
A Ddrm-uapi.rst254 have succeeded before the disappearance. See also about memory maps
258 with ENODEV or succeed if it would have succeeded without the

Completed in 45 milliseconds

123