Searched full:successfully (Results 1 – 25 of 209) sorted by relevance
123456789
| /Documentation/ABI/testing/ |
| D | procfs-diskstats | 13 4 reads completed successfully
30 15 discards completed successfully
39 19 flush requests completed successfully
|
| D | sysfs-bus-fsi-devices-sbefifo | 10 has, more recent transfers have completed successfully.
|
| D | sysfs-driver-ge-achc | 8 has either been flashed successfully or an error occurred.
|
| D | sysfs-devices-waiting_for_supplier | 8 removed once a device probes successfully (because the
|
| D | sysfs-devices-online | 20 type's .online() is executed successfully.
|
| D | sysfs-devices-state_synced | 20 and have probed successfully. Resources that were left disabled
|
| D | ppc-memtrace | 17 debugfs files will be created. Once memory is successfully
|
| /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.
|
| /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
|
| /Documentation/translations/zh_CN/maintainer/ |
| D | pull-requests.rst | 94 this in a way to successfully neutralize the problems.
98 All of these patches have been successfully tested in the latest
|
| /Documentation/admin-guide/mm/ |
| D | transhuge.rst | 423 monitor how successfully the system is providing huge pages for use.
426 is incremented every time a huge page is successfully
432 successfully allocated a new huge page to store the data.
449 is incremented every time a shmem huge page is successfully
498 successfully allocated. Note, it doesn't count every map of
520 is incremented every time a huge page is successfully
543 is incremented every time a shmem huge page is successfully
556 is incremented every time a huge page is successfully split into
|
| /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.
|
| /Documentation/userspace-api/media/dvb/ |
| D | net-add-if.rst | 37 the system call successfully returns, a new virtual network interface is
|
| /Documentation/admin-guide/blockdev/ |
| D | nbd.rst | 21 the nbd-server has been successfully ported to other operating
|
| /Documentation/devicetree/ |
| D | changesets.rst | 36 If a successfully applied changeset needs to be removed, it can be done
|
| /Documentation/admin-guide/mm/damon/ |
| D | lru_sort.rst | 235 Number of hot memory regions that successfully be LRU-sorted.
240 Total bytes of hot memory regions that successfully be LRU-sorted.
260 Number of cold memory regions that successfully be LRU-sorted.
265 Total bytes of cold memory regions that successfully be LRU-sorted.
|
| /Documentation/netlink/specs/ |
| D | netdev.yaml | 319 Number of wire packets successfully received and passed to the stack.
326 doc: Successfully received bytes, see `rx-packets`.
331 Number of wire packets successfully sent. Packet is considered to be
332 successfully sent once it is in device memory (usually this means
337 doc: Successfully sent bytes, see `tx-packets`.
|
| /Documentation/devicetree/bindings/media/ |
| D | nxp,dw100.yaml | 17 processing, it successfully generates a corrected output image.
|
| /Documentation/livepatch/ |
| D | callbacks.rst | 87 - Refuse to load a module, if the livepatch was already successfully
98 If the object did successfully patch, but the patch transition never
|
| /Documentation/translations/zh_CN/dev-tools/ |
| D | gcov.rst | 230 echo "$DEST successfully created, copy to test system and unpack with:"
263 echo "$DEST successfully created, copy to build system and unpack with:"
|
| /Documentation/process/ |
| D | submit-checklist.rst | 87 c) Builds successfully when using ``O=builddir``
89 d) Any Documentation/ changes build successfully without new warnings/errors.
|
| D | email-clients.rst | 61 and successfully apply it with 'patch' before sending patches to Linux
95 Works. Some people use this successfully for patches.
108 Some people use this successfully for patches.
124 Some people use Kmail successfully for patches.
|
| /Documentation/translations/zh_TW/dev-tools/ |
| D | gcov.rst | 230 echo "$DEST successfully created, copy to test system and unpack with:"
263 echo "$DEST successfully created, copy to build system and unpack with:"
|
| /Documentation/networking/device_drivers/ethernet/altera/ |
| D | altera_tse.rst | 159 Section 5.2.2.1.2. This statistics is the count of frames that are successfully
163 Section 5.2.2.1.5. This statistic is the count of frames that are successfully
179 successfully transmitted from the interface.
183 successfully received by the controller.
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-request-alloc.rst | 39 If the request was successfully allocated, then the request file descriptor
|
123456789