Searched full:response (Results 1 – 25 of 236) sorted by relevance
12345678910
| /Documentation/process/ |
| D | embargoed-hardware-issues.rst | 99 will form the initial response team for a particular issue. The initial
100 response team can bring in further developers (domain experts) to address
143 form the initial response team and will be responsible for handling the
145 response team, but is not necessarily involved in the mitigation
164 entity or member of an listed entity, then the response teams can
166 that the expert is also part of the entity's response team.
171 The disclosing party provides detailed information to the initial response
181 The initial response team sets up an encrypted mailing-list or repurposes
195 The initial response team will identify further experts from the Linux
226 to any individual who is not a member of the response team nor to any other
[all …]
|
| D | code-of-conduct.rst | 45 and are expected to take appropriate and fair corrective action in response to
70 and will result in a response that is deemed necessary and appropriate
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-ppi | 36 What: /sys/class/tpm/tpmX/ppi/response
40 This attribute shows the response to the most recent operation
41 request it acted upon. The format is "<request> <response num>
42 : <response description>".
|
| D | debugfs-scmi-raw | 9 Any subsequently received response can be read from this same
24 Any subsequently received response can be read from this same
26 Any additional delayed response received afterwards can be read
77 Any subsequently received response can be read from this same
101 Any subsequently received response can be read from this same
104 Any additional delayed response received afterwards can be read
|
| D | debugfs-wilco-ec | 22 response by reading from raw.
45 data are the actual response.
|
| D | sysfs-bus-papr-pmem | 9 response to H_SCM_HEALTH hcall. The details of the bit
10 flags returned in response to this hcall is available
|
| D | debugfs-olpc | 14 To read the response (if any), read from the generic node after executing
|
| /Documentation/driver-api/surface_aggregator/clients/ |
| D | cdev.rst | 116 ``payload.data`` and ``payload.length`` members. If a response is required,
117 the response buffer must be allocated by the caller and passed in via the
118 ``response.data`` member. The ``response.length`` member must be set to the
119 capacity of this buffer, or if no response is required, zero. Upon
120 completion of the request, the call will write the response to the response
122 actual size of the response, in bytes.
124 Additionally, if the request has a response, this must be indicated via the
|
| /Documentation/misc-devices/ |
| D | ibmvmc.rst | 73 This communication device uses Command/Response Queue (CRQ) and the
100 Command/Response Queue a facility which is used to communicate
135 CAPABILITIES RESPONSE
139 ADD BUFFER RESPONSE | - Perform # HMCs Iterations
156 connection. Finally, the hypervisor sends an Interface Open Response
169 Add Buffer Response | - Perform N Iterations
171 Interface Open Response
183 are currently available, EBUSY is returned in response to the write(). A
219 INTERFACE CLOSE RESPONSE
|
| /Documentation/networking/ |
| D | xfrm_sync.rst | 137 The response is a XFRM_MSG_NEWAE which is formatted based on what
140 The response will always have XFRMA_LTIME_VAL and XFRMA_REPLAY_VAL TLVs.
152 A response is issued back to the sender in user space to indicate success
158 ii) kernel->user direction as a response to XFRM_MSG_GETAE
160 The response will always have XFRMA_LTIME_VAL and XFRMA_REPLAY_VAL TLVs.
|
| D | mac80211-auth-assoc-deauth.txt | 32 driver->mac80211: RX probe response
60 driver->mac80211: RX assoc response
|
| D | secid.rst | 14 the incoming packet this flow is being generated as a response to (e.g. tcp
|
| /Documentation/devicetree/bindings/regulator/ |
| D | maxim,max8973.yaml | 76 description: Enable Enhanced Transient Response.
81 Enhanced transient response circuit is enabled and set for high
84 Enhanced transient response (ETR) will affect the configuration of CKADV.
|
| /Documentation/accel/qaic/ |
| D | aic100.rst | 94 channels, each consisting of a set of request/response FIFOs. Each active
246 FIFO is the request FIFO. The other FIFO is the response FIFO.
254 * Response FIFO head pointer (offset 0x8). Read/write by the host. Indicates
256 * Response FIFO tail pointer (offset 0xc). Read only by the host. Device
270 consume the beginning of the memory chunk, and the response FIFO will consume
303 request ID. A request FIFO element and a response FIFO element with
317 shall generate a response FIFO element when this request is
389 Response FIFO
392 Once a request is fully processed, a response FIFO element is generated if
393 specified in pcie_dma_cmd. The structure of a response FIFO element:
[all …]
|
| /Documentation/driver-api/surface_aggregator/ |
| D | ssh.rst | 249 EC in response to a request), and events (sent by the EC without a preceding
263 response to a request should have the same target category, command ID, and
269 request-response pair does not match. Only the request ID has to match.
272 response. Not all commands produce a response, and this is not detectable by
274 response (or signal this to the communication framework, as is done in
292 (``TID``). Note that a response to a specific request therefore has the source
294 target is the response source and the request source is the response target).
315 commands (ACKed frame but no command response) has been observed. For five
|
| D | internal.rst | 316 Requests can have an optional response that is equally sent via a SSH
318 the request must know if a response is expected and mark this in the request
320 can wait for this response.
325 layer via |ssh_rtl_submit|. For a request without a response, successful
328 completion callback). For a request with response, successful completion
329 will occur once the response has been received and matched to the request
376 requests, i.e. requests awaiting a response from the EC (similar to what the
386 requests can be pending, i.e. waiting for a response, at the same time. If
387 the request requires a response, the request is added to the pending set
399 If the request expects a response, it is marked as transmitted and the
[all …]
|
| D | overview.rst | 70 response from the EC (explicitly associated with the request), and events
72 being a direct response to a previous request. We may also refer to requests
73 without response as commands. In general, events need to be enabled via one
|
| D | client.rst | 165 that the caller provides an argument to the SAM EC and receives a response.
166 The caller needs to know the (maximum) length of the response payload and
170 EC is provided in little-endian format and, similarly, any response payload
201 /* Initialize request response. */
207 * Perform actual request. The response pointer may be null in case
208 * the request does not have any response. This must be consistent
224 * Convert request response back to native format. Note that in the
|
| /Documentation/i2c/ |
| D | slave-testunit-backend.rst | 184 default response::
201 - response value (7 MSBs interpreted as I2C address)
213 The following command will trigger the alert with a response of 0xc9 after 1
224 hardware and, thus, may not be able to react to the response of the host fast
234 on the SMBus Alert Response Address (0x0c). It will reassign its original
|
| /Documentation/driver-api/nfc/ |
| D | nfc-hci.rst | 23 context blocks waiting for response) or asynchronously (the response is returned
213 Completes execution in case of response timeout.
234 the response.
244 able to complete the command with a timeout error if no response arrive.
250 form complete HCI frames, which can be a response, command, or event.
253 waiting command execution. Response processing involves invoking the completion
|
| /Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra234-cbb.yaml | 33 If the Error Response Disable (ERD) is set/enabled for an initiator,
34 then SError or Data abort exception error response is masked and an
|
| /Documentation/doc-guide/ |
| D | maintainer-profile.rst | 40 Patches can be sent anytime, but response will be slower than usual during
49 the work on my own time, so the response to patches will occasionally be
|
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-intel-ipu3.rst | 22 Saturation measure) cells, AWB filter response, AF (Auto-focus) filter response,
|
| /Documentation/arch/arm64/ |
| D | tagged-pointers.rst | 64 are not preserved in response to synchronous tag check faults
69 For signals raised in response to watchpoint debug exceptions, the
|
| /Documentation/userspace-api/netlink/ |
| D | intro-specs.rst | 109 // 0. Request and response pointers
129 // ... do stuff with the response @d
131 // 7. Free response
|
12345678910