| /linux/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-class-rtrs-client | 60 Operation is blocking and returns 0 if reconnect was successful.
134 Description: Contains 2 unsigned int values, the first one records number of successful
|
| /linux/tools/testing/selftests/drivers/net/hw/ |
| H A D | rss_input_xfrm.py | 48 successful = 0
59 successful += 1
60 if successful == 10:
|
| /linux/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/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/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/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/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/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/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/drivers/gpu/drm/xe/tests/ |
| H A D | xe_bo.c | 453 unsigned int interrupted = 0, successful = 0, count = 0; in shrink_test_run_device() local
591 successful++; in shrink_test_run_device()
599 interrupted, successful); in shrink_test_run_device()
|
| /linux/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.
|
| H A D | anchors.rst | 33 an URB is finished by (successful) completion. Thus disassociation
|
| /linux/Documentation/ |
| H A D | atomic_bitops.txt | 63 Except for a successful test_and_set_bit_lock() which has ACQUIRE semantics,
|
| /linux/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/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 messages
|
| /linux/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/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
|
| /linux/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/Documentation/security/keys/ |
| H A D | core.rst | 417 The ID of the new or updated key is returned if successful.
473 The ID of the new session keyring is returned if successful.
537 successful.
539 If successful, a string is placed in the buffer in the following format::
601 successful and write permission on both keyrings. Any errors that can
731 The old default will be returned if successful and error EINVAL will be
797 successful.
834 successful.
954 If successful, 0 is returned. If the key is not an asymmetric key,
1029 If successful, encrypt, decrypt and sign all return the amount of data
[all …]
|
| /linux/Documentation/virt/coco/ |
| H A D | tdx-guest.rst | 27 :Output: Upon successful execution, TDREPORT data is copied to
|
| /linux/tools/memory-model/ |
| H A D | lock.cat | 16 * LKR Lock-Read: the read part of a spin_lock() or successful
18 * LKW Lock-Write: the write part of a spin_lock() or successful
|
| /linux/Documentation/arch/powerpc/ |
| H A D | pmu-ebb.rst | 102 this case the enable will be successful. However if there is already an event
103 pinned on the PMU then the enable will not be successful.
|