Searched refs:acknowledgment (Results 1 – 17 of 17) sorted by relevance
| /linux/LICENSES/deprecated/ |
| A D | Zlib | 23 product, an acknowledgment in the product documentation would be appreciated
|
| /linux/arch/arm/mach-s3c/ |
| A D | irq-s3c24xx-fiq.S | 35 @ and an offset to the irq acknowledgment word
|
| /linux/block/ |
| A D | opal_proto.h | 234 __be32 acknowledgment; member
|
| /linux/Documentation/devicetree/bindings/mailbox/ |
| A D | fsl,mu.yaml | 67 acknowledgment support.
|
| /linux/Documentation/driver-api/surface_aggregator/ |
| A D | internal.rst | 67 acknowledgment (ACKing), packet (retransmission) timeouts, and relaying
170 been transmitted, but wait for acknowledgment (e.g. the corresponding ACK
174 re-submitted due to a packet acknowledgment timeout or NAK. On such a
222 The packet acknowledgment timeout is a per-packet timeout for sequenced
242 Note that due to transmission and packet acknowledgment timeouts, the packet
425 This timeout is, similar to the packet acknowledgment timeout on the packet
434 acknowledgment timeouts, guarantees that the request layer will always make
|
| /linux/Documentation/virt/kvm/ |
| A D | cpuid.rst | 92 async pf acknowledgment msr
|
| A D | msr.rst | 372 Asynchronous page fault (APF) acknowledgment.
|
| /linux/Documentation/virt/kvm/devices/ |
| A D | xive.rst | 29 handle priority management and interrupt acknowledgment. The most
|
| /linux/Documentation/mhi/ |
| A D | mhi.rst | 19 protocol provides data acknowledgment feature and manages the power state of the
|
| /linux/scripts/ |
| A D | spelling.txt | 53 acknowldegement||acknowledgment
54 acknowledgement||acknowledgment
|
| /linux/drivers/scsi/lpfc/ |
| A D | lpfc_hw.h | 2240 uint32_t acknowledgment:1; member
2254 uint32_t acknowledgment:1;
|
| /linux/Documentation/networking/ |
| A D | rds.rst | 196 piggybacked acknowledgment of last packet received
|
| A D | ip-sysctl.rst | 217 acknowledgment, which means the route was installed in the kernel,
460 (b) out-of-window acknowledgment number, or
517 which have not received an acknowledgment from connecting client.
1914 acknowledgment, which means the route was installed in the kernel,
2867 acknowledgment to a probe packet. This is also the time interval
|
| A D | timestamping.rst | 140 cumulative acknowledgment. The mechanism ignores SACK and FACK.
|
| A D | rxrpc.rst | 149 (#) There are two types of positive acknowledgment: hard-ACKs and soft-ACKs.
|
| /linux/Documentation/filesystems/ |
| A D | autofs.rst | 415 and no acknowledgment is needed.
|
| /linux/Documentation/admin-guide/ |
| A D | reporting-issues.rst | 1451 then should at least have sent some kind of acknowledgment.
|
Completed in 51 milliseconds