Home
last modified time | relevance | path

Searched refs:explanation (Results 1 – 25 of 124) sorted by relevance

12345

/openbmc/linux/drivers/nvme/host/
H A Dfc.h50 u8 reason, u8 explanation, u8 vendor) in nvme_fc_format_rjt() argument
60 rjt->rjt.reason_explanation = explanation; in nvme_fc_format_rjt()
/openbmc/linux/tools/testing/vsock/
H A DREADME54 Output explanation:
67 Output explanation:
/openbmc/linux/Documentation/driver-api/
H A Dzorro.rst35 "My explanation"))
48 "My explanation"))
/openbmc/linux/tools/memory-model/Documentation/
H A DREADME36 rationale, and implementation: explanation.txt
57 explanation.txt
/openbmc/linux/Documentation/translations/zh_CN/core-api/
H A Drefcount-vs-atomic.rst25 本文档中使用的术语尽量遵循tools/memory-model/Documentation/explanation.txt
/openbmc/linux/drivers/scsi/lpfc/
H A Dlpfc_nl.h86 uint32_t explanation; member
/openbmc/linux/drivers/scsi/qla2xxx/
H A Dqla_nvme.c1088 u8 explanation, u8 vendor) in qla_nvme_fc_format_rjt() argument
1101 rjt->rjt.reason_explanation = explanation; in qla_nvme_fc_format_rjt()
1146 a->reason, a->explanation, 0); in qla_nvme_ls_reject_iocb()
1275 a.explanation = FCNVME_RJT_EXP_NONE; in qla2xxx_process_purls_iocb()
1285 a.explanation = FCNVME_RJT_EXP_NONE; in qla2xxx_process_purls_iocb()
1294 a.explanation = FCNVME_RJT_EXP_NONE; in qla2xxx_process_purls_iocb()
/openbmc/linux/drivers/net/usb/
H A Dhso.c645 char *explanation; in handle_usb_error() local
649 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 …]
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DMIT-enna7 Please see the COPYING.PLAIN for a plain-english explanation of this notice and it's intent.
H A DImlib27 Please see the COPYING-PLAIN for a plain-english explanation of this notice and its intent.
/openbmc/linux/net/caif/
H A DKconfig22 See Documentation/networking/caif for a further explanation on how to
/openbmc/linux/Documentation/devicetree/bindings/pci/
H A Dmobiveil-pcie.txt40 detailed explanation
H A Dmediatek-pcie.txt45 explanation.
70 explanation.
/openbmc/linux/Documentation/translations/zh_TW/admin-guide/
H A Dtainted-kernels.rst69 a more details explanation of the various taint flags.
/openbmc/linux/Documentation/translations/zh_CN/admin-guide/
H A Dtainted-kernels.rst66 a more details explanation of the various taint flags.
/openbmc/linux/Documentation/fb/
H A Daty128fb.rst62 explanation. Default is 640x480x8bpp.
H A Ddeferred_io.rst7 IO. The following example may be a useful explanation of how one such setup
/openbmc/linux/Documentation/ABI/stable/
H A Dsysfs-firmware-efi-vars32 explanation of each of these variables.
/openbmc/linux/Documentation/admin-guide/
H A Dinit.rst38 Please extend this explanation whenever you find new failure causes
/openbmc/linux/Documentation/userspace-api/media/drivers/
H A Domap3isp-uapi.rst165 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
/openbmc/qemu/docs/devel/testing/
H A Dqtest.rst33 Refer to :ref:`qgraph` for Qgraph explanation and API.
/openbmc/linux/Documentation/crypto/
H A Dintro.rst12 To understand and properly use the kernel crypto API a brief explanation
/openbmc/linux/Documentation/core-api/
H A Dgfp_mask-from-fs-io.rst48 explanation what is the reclaim context for easier maintenance.
/openbmc/linux/Documentation/admin-guide/cgroup-v1/
H A Dmemcg_test.rst65 Under below explanation, we assume CONFIG_SWAP=y.
114 But brief explanation of the behavior of memcg around shmem will be
/openbmc/u-boot/doc/
H A DREADME.i2c32 sure that the other side doesn't want it also. A detailed explanation is best

12345