Searched full:successfully (Results 1 – 25 of 1735) sorted by relevance
12345678910>>...70
| /linux-5.10/drivers/greybus/ |
| D | greybus_trace.h | 128 * has been successfully created.
139 * request has been successfully created and initialized.
199 * Occurs after a new connection is successfully created.
268 * Occurs after a new bundle is successfully created.
332 * Occurs after a new interface is successfully created.
352 * Occurs when a registered interface has been successfully
363 * Occurs when an interface has been successfully enabled.
405 * Occurs after a new module is successfully created, before
416 * Occurs after a module is successfully created, before registering
458 * Occurs after a new host device is successfully created, before
|
| /linux-5.10/tools/testing/selftests/ftrace/test.d/kprobe/ |
| D | kretprobe_maxactive.tc | 6 # Test if we successfully reject unknown messages
9 # Test if we successfully reject too big maxactive
12 # Test if we successfully reject unparsable numbers for maxactive
|
| /linux-5.10/lib/ |
| D | lockref.c | 61 * Return: 1 if count updated successfully or 0 if count was zero
89 * Return: 1 if count updated successfully or 0 if count would become zero
117 * Return: 1 if count updated successfully or 0 if count was zero
162 * Return: 1 if count updated successfully or 0 if count <= 1 and lock taken
197 * Return: 1 if count updated successfully or 0 if lockref was dead
|
| /linux-5.10/include/linux/ |
| D | hwspinlock.h | 179 * Returns 0 if we successfully locked the hwspinlock, -EBUSY if
199 * Returns 0 if we successfully locked the hwspinlock, -EBUSY if
218 * Returns 0 if we successfully locked the hwspinlock, -EBUSY if
235 * Returns 0 if we successfully locked the hwspinlock, -EBUSY if
255 * Returns 0 if we successfully locked the hwspinlock, -EBUSY if
277 * Returns 0 when the @hwlock was successfully taken, and an appropriate
300 * Returns 0 when the @hwlock was successfully taken, and an appropriate
323 * Returns 0 when the @hwlock was successfully taken, and an appropriate
345 * Returns 0 when the @hwlock was successfully taken, and an appropriate
370 * Returns 0 when the @hwlock was successfully taken, and an appropriate
|
| D | psp-sev.h | 494 * 0 if the SEV successfully processed the command
509 * 0 if the SEV successfully processed the command
531 * 0 if the SEV successfully processed the command
548 * 0 if the sev successfully processed the command
563 * 0 if the sev successfully processed the command
577 * 0 if the sev successfully processed the command
592 * 0 if the sev successfully processed the command
|
| D | dlm.h | 114 * 0 if request is successfully queued for processing
148 * when the resource is successfully unlocked.
157 * 0 if request is successfully queued for processing
|
| /linux-5.10/Documentation/admin-guide/ |
| D | iostats.rst | 66 This is the total number of reads completed successfully.
75 This is the total number of sectors read successfully.
82 This is the total number of writes completed successfully.
88 This is the total number of sectors written successfully.
113 This is the total number of discards completed successfully.
119 This is the total number of sectors discarded successfully.
126 This is the total number of flush requests completed successfully.
|
| /linux-5.10/Documentation/ABI/testing/ |
| D | procfs-diskstats | 13 4 reads completed successfully
30 15 discards completed successfully
39 19 flush requests completed successfully
|
| /linux-5.10/drivers/net/ethernet/intel/igbvf/ |
| D | mbx.c | 10 * returns SUCCESS if it successfully received a message notification
36 * returns SUCCESS if it successfully received a message acknowledgment
64 * returns SUCCESS if it successfully received a message notification and
90 * returns SUCCESS if it successfully copied message into the buffer and
237 * returns SUCCESS if it successfully copied message into the buffer
275 * returns SUCCESS if it successfully read message from buffer
|
| /linux-5.10/drivers/net/ethernet/intel/ixgbevf/ |
| D | mbx.c | 11 * returns 0 if it successfully received a message notification
34 * returns 0 if it successfully received a message acknowledgment
59 * returns 0 if it successfully received a message notification and
85 * returns 0 if it successfully copied message into the buffer and
226 * returns 0 if it successfully copied message into the buffer
262 * returns 0 if it successfully read message from buffer
|
| /linux-5.10/drivers/media/platform/mtk-vcodec/ |
| D | venc_drv_if.h | 133 * Return: 0 if creating handle successfully, otherwise it is failed.
140 * Return: 0 if releasing handle successfully, otherwise it is failed.
149 * Return: 0 if setting param successfully, otherwise it is failed.
162 * Return: 0 if encoding frame successfully, otherwise it is failed.
|
| /linux-5.10/drivers/net/ethernet/intel/ixgbe/ |
| D | ixgbe_mbx.c | 16 * returns SUCCESS if it successfully read message from buffer
39 * returns SUCCESS if it successfully copied message into the buffer
110 * returns SUCCESS if it successfully received a message notification
135 * returns SUCCESS if it successfully received a message acknowledgement
162 * returns SUCCESS if it successfully received a message notification and
189 * returns SUCCESS if it successfully copied message into the buffer and
330 * returns SUCCESS if it successfully copied message into the buffer
|
| /linux-5.10/tools/testing/selftests/arm64/signal/ |
| D | README | 15 executable is used for each test since many tests complete successfully
36 - Most of these tests are successfully passing if the process gets killed by
53 successfully progressed up to the stage of triggering the fake sigreturn
|
| /linux-5.10/drivers/media/platform/mtk-vpu/ |
| D | mtk_vpu.h | 90 * Return: Return 0 if ipi registers successfully, otherwise it is failed.
108 * Return: Return 0 if sending data successfully, otherwise it is failed.
135 * Return: Return 0 if the handler is added successfully,
166 * Return: Return 0 if downloading firmware successfully,
|
| /linux-5.10/arch/arc/include/asm/ |
| D | spinlock.h | 43 /* 1 - lock taken successfully */
108 /* 1 - lock taken successfully */
166 /* 1 - lock taken successfully */
243 /* 1 - lock taken successfully */
297 /* 1 - lock taken successfully */
321 /* 1 - lock taken successfully */
|
| /linux-5.10/drivers/net/ethernet/intel/igb/ |
| D | e1000_mbx.c | 14 * returns SUCCESS if it successfully read message from buffer
39 * returns SUCCESS if it successfully copied message into the buffer
132 * returns SUCCESS if it successfully received a message notification
161 * returns SUCCESS if it successfully received a message acknowledgement
192 * returns SUCCESS if it successfully received a message notification and
219 * returns SUCCESS if it successfully copied message into the buffer and
370 * returns SUCCESS if it successfully copied message into the buffer
|
| /linux-5.10/drivers/staging/media/atomisp/pci/runtime/queue/interface/ |
| D | ia_css_queue.h | 115 * @return 0 - Successfully access state.
128 * @return 0 - Successfully access state.
140 * @return 0 - Successfully access state.
154 * @return 0 - Successfully access state.
|
| /linux-5.10/Documentation/driver-api/driver-model/ |
| D | driver.rst | 163 When the driver has successfully bound itself to that device, then probe()
191 devices of the device have successfully probed. The list of consumers of the
198 point in time have already probed successfully, sync_state() is called right
204 still consumers that haven't probed successfully, the sync_state() call is
206 device probe successfully. If during the reattempt, the driver core finds that
|
| /linux-5.10/drivers/staging/media/atomisp/pci/runtime/eventq/interface/ |
| D | ia_css_eventq.h | 26 * @return 0 - Successfully dequeue.
44 * @return 0 - Successfully enqueue.
|
| /linux-5.10/Documentation/networking/ |
| D | tls-offload.rst | 55 successfully, the driver will set the decrypted bit in the associated
198 Note that resync is only attempted for connections which were successfully
274 Green segments are successfully decrypted, blue ones are passed
277 In above case segment 1 is received and decrypted successfully.
383 had been handled successfully and authenticated or the packet has to be passed
427 * ``rx_tls_decrypted_packets`` - number of successfully decrypted RX packets
430 which were successfully decrypted.
444 the driver was successfully handled.
|
| /linux-5.10/arch/arm64/kvm/hyp/ |
| D | vgic-v2-cpuif-proxy.c | 31 * 1: GICV access successfully performed
33 * -1: Illegal GICV access successfully performed
|
| /linux-5.10/tools/testing/selftests/x86/ |
| D | vdso_restorer.c | 73 printf("[OK]\tSA_SIGINFO handler returned successfully\n"); in main()
90 printf("[OK]\t!SA_SIGINFO handler returned successfully\n"); in main()
|
| /linux-5.10/include/xen/ |
| D | xen-ops.h | 129 * Returns the number of successfully mapped frames, or a -ve error
166 * Returns the number of successfully mapped frames, or a -ve error
191 * Returns the number of successfully mapped frames, or a -ve error
|
| /linux-5.10/include/xen/interface/ |
| D | memory.h | 17 * -ve errcode on failure, or the # extents successfully allocated or freed.
86 * [OUT] Number of input extents that were successfully exchanged:
87 * 1. The first @nr_exchanged input extents were successfully
90 * indicate the GMFNs that were successfully exchanged.
|
| /linux-5.10/Documentation/admin-guide/mm/ |
| D | transhuge.rst | 304 monitor how successfully the system is providing huge pages for use.
307 is incremented every time a huge page is successfully
313 successfully allocated a new huge page to store the data.
330 is incremented every time a file huge page is successfully
370 successfully allocated. It includes allocations which where
|
12345678910>>...70