| /linux/rust/kernel/sync/atomic/ |
| H A D | ordering.rs | 20 //! described in "DEPENDENCY RELATIONS" in [`LKMM`]'s [`explanation`].
23 //! [`explanation`]: srctree/tools/memory-model/Documentation/explanation.txt
|
| /linux/include/uapi/scsi/fc/ |
| H A D | fc_gs.h | 29 __u8 ct_explan; /* reason code explanation */
75 FC_FS_EXP_NONE = 0x00, /* no additional explanation */
|
| /linux/tools/memory-model/Documentation/ |
| H A D | README | 49 rationale, and implementation: explanation.txt and
75 explanation.txt
|
| /linux/Documentation/driver-api/ |
| H A D | zorro.rst | 35 "My explanation"))
48 "My explanation"))
|
| /linux/drivers/nvme/host/ |
| H A 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/arch/s390/include/asm/ |
| H A D | msi.h | 8 * IRQ_DOMAIN_FLAG_ISOLATED_MSI. See for an explanation how it works:
|
| /linux/Documentation/userspace-api/media/drivers/ |
| H A 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/net/caif/ |
| H A D | Kconfig | 22 See Documentation/networking/caif for a further explanation on how to
|
| /linux/drivers/net/can/rockchip/ |
| H A D | rockchip_canfd-rx.c | 176 * explanation. in rkcanfd_rxstx_filter()
252 * explanation. in rkcanfd_handle_rx_int_one()
|
| /linux/drivers/scsi/lpfc/ |
| H A 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/kernel/trace/ |
| H A D | tracing_map.h | 33 * explanation of that data structure in the discussion of the
99 * benefit from some minimal explanation.
|
| /linux/Documentation/trace/ |
| H A D | index.rst | 46 A detailed explanation of event tracing mechanisms and their
|
| /linux/drivers/scsi/bfa/ |
| H A 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/drivers/scsi/qla2xxx/ |
| H A 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/Documentation/admin-guide/ |
| H A D | init.rst | 38 Please extend this explanation whenever you find new failure causes
|
| /linux/Documentation/crypto/ |
| H A D | intro.rst | 12 To understand and properly use the kernel crypto API a brief explanation
|
| /linux/include/linux/ |
| H A D | fault-inject.h | 18 * For explanation of the elements of this struct, see
|
| /linux/Documentation/networking/ |
| H A 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/drivers/net/usb/ |
| H A D | hso.c | 644 char *explanation; in handle_usb_error() local
648 explanation = "no device"; in handle_usb_error()
651 explanation = "endpoint not enabled"; in handle_usb_error()
654 explanation = "endpoint stalled"; in handle_usb_error()
657 explanation = "not enough bandwidth"; in handle_usb_error()
660 explanation = "device disabled"; in handle_usb_error()
663 explanation = "device suspended"; in handle_usb_error()
669 explanation = "internal error"; in handle_usb_error()
675 explanation = "protocol error"; in handle_usb_error()
680 explanation = "unknown status"; in handle_usb_error()
[all …]
|
| /linux/tools/include/uapi/ |
| H A D | README | 43 Another explanation from Ingo Molnar:
|
| /linux/Documentation/devicetree/bindings/pci/ |
| H A D | mediatek-pcie.txt | 45 explanation.
70 explanation.
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | memcg_test.rst | 65 Under below explanation, we assume CONFIG_SWAP=y.
114 But brief explanation of the behavior of memcg around shmem will be
|
| /linux/Documentation/hwmon/ |
| H A D | lm63.rst | 60 An explanation from National Semiconductor: The two lower bits of the read
|
| /linux/Documentation/fb/ |
| H A D | deferred_io.rst | 7 IO. The following example may be a useful explanation of how one such setup
|
| H A D | aty128fb.rst | 60 explanation. Default is 640x480x8bpp.
|