| /openbmc/linux/Documentation/filesystems/spufs/ |
| H A D | spufs.rst | 180 completing the string, regardless of changes to the register by
|
| /openbmc/linux/Documentation/block/ |
| H A D | data-integrity.rst | 163 The profile also contains a few constants to aid in completing,
|
| H A D | ublk.rst | 38 driver, thus completing the request cycle. This way, any specific IO handling
|
| /openbmc/bmcweb/ |
| H A D | COMMON_ERRORS.md | 317 completing, which cannot be guaranteed, and has many time caused bugs.
|
| /openbmc/docs/designs/ |
| H A D | redfish-spdm-attestation.md | 209 for completing CSR request).
|
| H A D | firmware-update-via-blobs.md | 100 `/flash/bios` without completing (or later aborting) the first update process
|
| /openbmc/qemu/docs/devel/ |
| H A D | memory.rst | 349 rather than completing successfully; those devices can use the
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | dwc3.rst | 628 completing it. With these two events, we can see how a ``TRB`` changes
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | scsi_eh.rst | 327 contains invalid sense data when error-completing the scmd
|
| H A D | scsi_fc_transport.rst | 340 the physical port completing its initialization relative to the
|
| H A D | ChangeLog.megaraid | 552 iv. scsi_host_put(), do just before completing HBA shutdown.
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | access-marking.txt | 420 prevents begin_global() from completing. It is therefore safe to invoke
|
| H A D | litmus-tests.txt | 317 P1() is the other side completing its update.
|
| /openbmc/openbmc/poky/documentation/toaster-manual/ |
| H A D | setup-and-use.rst | 169 After completing these steps, the following confirmation message
|
| /openbmc/docs/ |
| H A D | CONTRIBUTING.md | 177 get that accepted before completing the details.
|
| /openbmc/linux/Documentation/RCU/Design/Data-Structures/ |
| H A D | Data-Structures.rst | 471 | #. But CPU 1 beats it to the punch, completing the current grace |
513 completing. If either of these two pointers is referencing a task that
|
| /openbmc/linux/Documentation/driver-api/dmaengine/ |
| H A D | provider.rst | 459 completion and is completing the operation out of order.
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | stallwarn.rst | 60 RCU grace periods from ever completing. Either way, the
|
| /openbmc/linux/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| H A D | Expedited-Grace-Periods.rst | 385 Execution will continue with Tasks E and H completing their grace
|
| /openbmc/linux/Documentation/driver-api/surface_aggregator/ |
| H A D | internal.rst | 208 to the corresponding pending packet (via sequence ID) and completing it, as
|
| /openbmc/qemu/hw/net/ |
| H A D | trace-events | 325 sungem_tx_finished(uint32_t size) "TX completing %"PRIu32 " bytes packet"
|
| /openbmc/phosphor-mboxd/Documentation/ |
| H A D | mbox_protocol.md | 147 prior to completing the response may lead to a data race, and must, therefore,
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | start.rst | 35 essential to completing subsequent steps, which are to get your
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | boot.rst | 1321 After completing your hook, you should jump to the address
|
| /openbmc/linux/drivers/scsi/aic7xxx/ |
| H A D | aic7xxx.seq | 63 * this list every time a request sense occurs or after completing a non-tagged
|