| /linux-6.15/tools/testing/selftests/drivers/net/hw/ |
| H A D | rss_input_xfrm.py | 43 successful = 0
54 successful += 1
55 if successful == 10:
|
| /linux-6.15/Documentation/ABI/testing/ |
| H A D | sysfs-devices-online | 11 successful) its 'offline' field is updated accordingly. In
14 for the device and (if successful) its 'offline' field is
17 After a successful execution of the bus type's .offline()
|
| H A D | configfs-acpi | 23 successful the user must check the error code
24 for close(). If the operation is successful,
|
| H A D | sysfs-platform-mellanox-bootctl | 151 A successful write to this attribute will latch the
160 A successful read from this attribute returns the status of
162 also cleared upon successful read operation.
|
| /linux-6.15/Documentation/filesystems/ |
| H A D | gfs2-uevents.rst | 19 is successful, an ONLINE uevent will follow. If it is not successful
30 The ONLINE uevent is generated after a successful mount or remount. It
40 successful mount of the filesystem by the first node (FIRSTMOUNT=Done).
58 uevent for a successful mount or remount.
|
| /linux-6.15/Documentation/locking/ |
| H A D | hwspinlock.rst | 95 Upon a successful return from this function, preemption is disabled so
100 Returns 0 when successful and an appropriate error code otherwise (most
111 Upon a successful return from this function, preemption and the local
115 Returns 0 when successful and an appropriate error code otherwise (most
127 Upon a successful return from this function, preemption is disabled,
132 Returns 0 when successful and an appropriate error code otherwise (most
178 Upon a successful return from this function, preemption is disabled so
195 Upon a successful return from this function, preemption and the local
211 Upon a successful return from this function, preemption is disabled,
268 Upon a successful return from this function, preemption and local
[all …]
|
| /linux-6.15/Documentation/w1/slaves/ |
| H A D | w1_ds2423.rst | 28 was successful and CRC matched.
29 If the operation was successful, there is also in the end of each line
42 example from the successful read::
|
| /linux-6.15/drivers/md/dm-vdo/ |
| H A D | errors.c | 15 static const struct error_info successful = { "UDS_SUCCESS", "Success" }; variable
102 *info_ptr = &successful; in get_error_info()
|
| /linux-6.15/Documentation/litmus-tests/atomic/ |
| H A D | cmpxchg-fail-unordered-2.litmus | 7 * an acquire release operation. (In contrast, a successful cmpxchg()
|
| H A D | cmpxchg-fail-unordered-1.litmus | 7 * full barrier. (In contrast, a successful cmpxchg() does act as a
|
| /linux-6.15/Documentation/core-api/ |
| H A D | debug-objects.rst | 61 successful fixups along with information about the usage of the internal
221 The function returns true when the fixup was successful, otherwise
240 The function returns true when the fixup was successful, otherwise
266 The function returns true when the fixup was successful, otherwise
282 The function returns true when the fixup was successful, otherwise
295 The function returns true when the fixup was successful, otherwise
|
| /linux-6.15/Documentation/driver-api/soundwire/ |
| H A D | stream.rst | 285 After all above operations are successful, stream state is set to
315 After all above operations are successful, stream state is set to
365 After all above operations are successful, stream state is set to
397 After all above operations are successful, stream state is set to
425 After all above operations are successful, stream state is set to
458 After all above operations are successful, stream state is set to
492 After all above operations are successful, stream state is set to
|
| /linux-6.15/Documentation/networking/ |
| H A D | lapb-module.rst | 116 successful then LAPB_OK is returned. The token must be a unique identifier
153 LAPB_OK LAPB getparms was successful.
168 LAPB_OK LAPB getparms was successful.
203 is successful then the skbuff is owned by the LAPB module and may not be
218 to the beginning of the LAPB data. If the call is successful then the skbuff
|
| /linux-6.15/arch/arm/nwfpe/ |
| H A D | entry.S | 83 cmp r0, #0 @ was emulation successful
124 @ r4 = PC value to resume execution after successful emulation
|
| /linux-6.15/Documentation/usb/ |
| H A D | usbip_protocol.rst | 35 import was successful the TCP/IP connection remains open and will be used
88 For UNLINK, note that after a successful USBIP_RET_UNLINK, the unlinked URB
383 | 0x14 | 4 | status: zero for successful URB transaction, |
432 | | | When UNLINK is successful, status is -ECONNRESET; |
|
| /linux-6.15/drivers/gpu/drm/xe/tests/ |
| H A D | xe_bo.c | 451 unsigned int interrupted = 0, successful = 0, count = 0; in shrink_test_run_device() local
589 successful++; in shrink_test_run_device()
597 interrupted, successful); in shrink_test_run_device()
|
| /linux-6.15/Documentation/arch/s390/ |
| H A D | monreader.rst | 164 within one data set and the end of each data set is indicated by a successful
182 should discard the data read since the last successful read with 0 size.
185 discard the data read since the last successful read with 0 size.
191 message limit reached, the data read since the last successful
|
| /linux-6.15/Documentation/ |
| H A D | atomic_bitops.txt | 63 Except for a successful test_and_set_bit_lock() which has ACQUIRE semantics,
|
| /linux-6.15/Documentation/userspace-api/media/dvb/ |
| H A D | fe-set-frontend.rst | 37 The result of this call will be successful if the parameters were valid
|
| /linux-6.15/Documentation/driver-api/usb/ |
| H A D | typec.rst | 78 After successful connection of a partner, the port driver needs to register the
88 successful, or NULL.
102 After successful connection of a cable that supports USB Power Delivery
121 the registration is successful, or NULL if it isn't.
|
| /linux-6.15/tools/testing/selftests/rcutorture/bin/ |
| H A D | parse-console.sh | 111 …echo $title no success message, `grep --binary-files=text 'ver:' $file | wc -l` successful version…
|
| /linux-6.15/Documentation/driver-api/tty/ |
| H A D | n_gsm.rst | 60 and check that it's successful (should return OK) */
112 mode. This may prevent a successful re-opening of the port later. To avoid
|
| /linux-6.15/Documentation/virt/coco/ |
| H A D | tdx-guest.rst | 27 :Output: Upon successful execution, TDREPORT data is copied to
|
| /linux-6.15/Documentation/power/ |
| H A D | userland-swsusp.rst | 73 will contain the result if the call is successful)
78 will contain the result if the call is successful)
83 will contain the swap page offset if the call is successful)
|
| /linux-6.15/Documentation/filesystems/caching/ |
| H A D | backend-api.rst | 73 If successful, the cache backend can then start setting up the cache. In the
289 If successful, it can set ``cache_priv`` to its own data.
308 True should be returned if successful and false otherwise. If false is
320 If successful, ``cookie->cache_priv`` can be set.
361 this object and start afresh. It should return true if successful and
|