/linux-6.14.4/include/uapi/scsi/fc/ |
D | fc_gs.h | 29 __u8 ct_explan; /* reason code explanation */ 75 FC_FS_EXP_NONE = 0x00, /* no additional explanation */
|
/linux-6.14.4/tools/memory-model/Documentation/ |
D | README | 46 rationale, and implementation: explanation.txt and 72 explanation.txt
|
/linux-6.14.4/tools/testing/vsock/ |
D | README | 69 Output explanation: 82 Output explanation:
|
/linux-6.14.4/Documentation/driver-api/ |
D | zorro.rst | 35 "My explanation")) 48 "My explanation"))
|
/linux-6.14.4/drivers/nvme/host/ |
D | fc.h | 50 u8 reason, u8 explanation, u8 vendor) in nvme_fc_format_rjt() argument 60 rjt->rjt.reason_explanation = explanation; in nvme_fc_format_rjt()
|
/linux-6.14.4/arch/s390/include/asm/ |
D | msi.h | 8 * IRQ_DOMAIN_FLAG_ISOLATED_MSI. See for an explanation how it works:
|
/linux-6.14.4/include/linux/ |
D | timer.h | 175 * See timer_delete_sync() for detailed explanation. 192 * See timer_delete() for detailed explanation.
|
D | fault-inject.h | 18 * For explanation of the elements of this struct, see
|
/linux-6.14.4/Documentation/userspace-api/media/drivers/ |
D | omap3isp-uapi.rst | 165 to have an in-depth knowledge of the hardware. Most of the fields explanation 167 configure private IOCTLs require explanation for better understanding as they
|
/linux-6.14.4/net/caif/ |
D | Kconfig | 22 See Documentation/networking/caif for a further explanation on how to
|
/linux-6.14.4/drivers/net/can/rockchip/ |
D | rockchip_canfd-rx.c | 176 * explanation. in rkcanfd_rxstx_filter() 252 * explanation. in rkcanfd_handle_rx_int_one()
|
/linux-6.14.4/drivers/scsi/lpfc/ |
D | lpfc_ct.c | 215 ct_rsp->Explanation = SLI_CT_NO_ADDITIONAL_EXPL; in lpfc_ct_reject_event() 1040 && (CTrsp->Explanation == SLI_CT_NO_FC4_TYPES)) { in lpfc_cmpl_ct_cmd_gid_ft() 1047 (uint32_t) CTrsp->Explanation, in lpfc_cmpl_ct_cmd_gid_ft() 1054 (uint32_t) CTrsp->Explanation); in lpfc_cmpl_ct_cmd_gid_ft() 1062 (uint32_t) CTrsp->Explanation, in lpfc_cmpl_ct_cmd_gid_ft() 1069 (uint32_t) CTrsp->Explanation); in lpfc_cmpl_ct_cmd_gid_ft() 1080 (uint32_t) CTrsp->Explanation, in lpfc_cmpl_ct_cmd_gid_ft() 1087 (uint32_t) CTrsp->Explanation); in lpfc_cmpl_ct_cmd_gid_ft() 1252 && (CTrsp->Explanation == SLI_CT_NO_FC4_TYPES)) { in lpfc_cmpl_ct_cmd_gid_pt() 1259 (uint32_t)CTrsp->Explanation, in lpfc_cmpl_ct_cmd_gid_pt() [all …]
|
/linux-6.14.4/arch/arm64/include/uapi/asm/ |
D | ptrace.h | 197 * V-registers on big-endian systems: see sigcontext.h for more explanation. 316 * systems: see sigcontext.h for more explanation.
|
/linux-6.14.4/kernel/trace/ |
D | tracing_map.h | 33 * explanation of that data structure in the discussion of the 99 * benefit from some minimal explanation.
|
/linux-6.14.4/fs/isofs/ |
D | util.c | 58 * results this may be the explanation. If enough people in iso_date()
|
/linux-6.14.4/Documentation/admin-guide/ |
D | init.rst | 38 Please extend this explanation whenever you find new failure causes
|
D | tainted-kernels.rst | 66 a more details explanation of the various taint flags. 109 More detailed explanation for tainting
|
/linux-6.14.4/Documentation/crypto/ |
D | intro.rst | 12 To understand and properly use the kernel crypto API a brief explanation
|
/linux-6.14.4/drivers/scsi/qla2xxx/ |
D | qla_nvme.c | 1087 u8 explanation, u8 vendor) in qla_nvme_fc_format_rjt() argument 1100 rjt->rjt.reason_explanation = explanation; in qla_nvme_fc_format_rjt() 1145 a->reason, a->explanation, 0); in qla_nvme_ls_reject_iocb() 1274 a.explanation = FCNVME_RJT_EXP_NONE; in qla2xxx_process_purls_iocb() 1284 a.explanation = FCNVME_RJT_EXP_NONE; in qla2xxx_process_purls_iocb() 1293 a.explanation = FCNVME_RJT_EXP_NONE; in qla2xxx_process_purls_iocb()
|
/linux-6.14.4/drivers/scsi/bfa/ |
D | bfa_fc.h | 466 * see FC-PH-X table 113 & 115 for explanation also FCP table 8 647 u32 reason_code_expl:8; /* Reason code explanation */ 664 * LS_RJT reason code explanation 722 u32 reason_expl:8; /* reason code explanation */ 1147 u32 exp_code:8; /* explanation code */ 1243 * definitions for the explanation code for all servers
|
/linux-6.14.4/Documentation/fb/ |
D | aty128fb.rst | 62 explanation. Default is 640x480x8bpp.
|
D | deferred_io.rst | 7 IO. The following example may be a useful explanation of how one such setup
|
/linux-6.14.4/tools/include/uapi/ |
D | README | 43 Another explanation from Ingo Molnar:
|
/linux-6.14.4/Documentation/networking/ |
D | snmp_counter.rst | 317 explanation below:: 327 explanation below:: 335 explanation below:: 352 Note: The above explanation is based on kernel 4.10 or above version, on 417 code provides a good explanation of them, I pasted them below:: 701 has additional explanation: 983 For details of challenge ACK, please refer the explanation of 1356 The explanation of the test: after run server_orphan.py and 1371 An additional explanation about orphan socket count: You could find the
|
/linux-6.14.4/Documentation/core-api/ |
D | gfp_mask-from-fs-io.rst | 48 explanation what is the reclaim context for easier maintenance.
|