Searched refs:explanation (Results 1 – 25 of 86) sorted by relevance
1234
50 u8 reason, u8 explanation, u8 vendor) in nvme_fc_format_rjt() argument60 rjt->rjt.reason_explanation = explanation; in nvme_fc_format_rjt()
16 2.1 struct request members explanation25 Short explanation of request members
36 rationale, and implementation: explanation.txt57 explanation.txt
35 "My explanation"))48 "My explanation"))
25 本文档中使用的术语尽量遵循tools/memory-model/Documentation/explanation.txt
86 uint32_t explanation; member
645 char *explanation; in handle_usb_error() local649 explanation = "no device"; in handle_usb_error()652 explanation = "endpoint not enabled"; in handle_usb_error()655 explanation = "endpoint stalled"; in handle_usb_error()658 explanation = "not enough bandwidth"; in handle_usb_error()661 explanation = "device disabled"; in handle_usb_error()664 explanation = "device suspended"; in handle_usb_error()670 explanation = "internal error"; in handle_usb_error()676 explanation = "protocol error"; in handle_usb_error()681 explanation = "unknown status"; in handle_usb_error()[all …]
22 See Documentation/networking/caif for a further explanation on how to
40 detailed explanation
18 detailed explanation
26 detailed explanation
45 explanation.70 explanation.
66 a more details explanation of the various taint flags.
69 a more details explanation of the various taint flags.
62 explanation. Default is 640x480x8bpp.
7 IO. The following example may be a useful explanation of how one such setup
32 explanation of each of these variables.
38 Please extend this explanation whenever you find new failure causes
165 to have an in-depth knowledge of the hardware. Most of the fields explanation167 configure private IOCTLs require explanation for better understanding as they
28 sure that the other side doesn't want it also. A detailed explanation is best
12 To understand and properly use the kernel crypto API a brief explanation
48 explanation what is the reclaim context for easier maintenance.
65 Under below explanation, we assume CONFIG_MEM_RES_CTRL_SWAP=y.114 But brief explanation of the behavior of memcg around shmem will be
60 An explanation from National Semiconductor: The two lower bits of the read
148 For more detailed explanation of every field, please refer to UEFI