/openbmc/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()
|
/openbmc/linux/tools/testing/vsock/ |
H A D | README | 54 Output explanation: 67 Output explanation:
|
/openbmc/linux/Documentation/driver-api/ |
H A D | zorro.rst | 35 "My explanation")) 48 "My explanation"))
|
/openbmc/linux/tools/memory-model/Documentation/ |
H A D | README | 36 rationale, and implementation: explanation.txt 57 explanation.txt
|
/openbmc/linux/Documentation/translations/zh_CN/core-api/ |
H A D | refcount-vs-atomic.rst | 25 本文档中使用的术语尽量遵循tools/memory-model/Documentation/explanation.txt
|
/openbmc/linux/drivers/scsi/lpfc/ |
H A D | lpfc_nl.h | 86 uint32_t explanation; member
|
/openbmc/linux/drivers/scsi/qla2xxx/ |
H A D | qla_nvme.c | 1088 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 D | hso.c | 645 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 D | MIT-enna | 7 Please see the COPYING.PLAIN for a plain-english explanation of this notice and it's intent.
|
H A D | Imlib2 | 7 Please see the COPYING-PLAIN for a plain-english explanation of this notice and its intent.
|
/openbmc/linux/net/caif/ |
H A D | Kconfig | 22 See Documentation/networking/caif for a further explanation on how to
|
/openbmc/linux/Documentation/devicetree/bindings/pci/ |
H A D | mobiveil-pcie.txt | 40 detailed explanation
|
H A D | mediatek-pcie.txt | 45 explanation. 70 explanation.
|
/openbmc/linux/Documentation/translations/zh_TW/admin-guide/ |
H A D | tainted-kernels.rst | 69 a more details explanation of the various taint flags.
|
/openbmc/linux/Documentation/translations/zh_CN/admin-guide/ |
H A D | tainted-kernels.rst | 66 a more details explanation of the various taint flags.
|
/openbmc/linux/Documentation/fb/ |
H A D | aty128fb.rst | 62 explanation. Default is 640x480x8bpp.
|
H A D | deferred_io.rst | 7 IO. The following example may be a useful explanation of how one such setup
|
/openbmc/linux/Documentation/ABI/stable/ |
H A D | sysfs-firmware-efi-vars | 32 explanation of each of these variables.
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | init.rst | 38 Please extend this explanation whenever you find new failure causes
|
/openbmc/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
|
/openbmc/qemu/docs/devel/testing/ |
H A D | qtest.rst | 33 Refer to :ref:`qgraph` for Qgraph explanation and API.
|
/openbmc/linux/Documentation/crypto/ |
H A D | intro.rst | 12 To understand and properly use the kernel crypto API a brief explanation
|
/openbmc/linux/Documentation/core-api/ |
H A D | gfp_mask-from-fs-io.rst | 48 explanation what is the reclaim context for easier maintenance.
|
/openbmc/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
|
/openbmc/u-boot/doc/ |
H A D | README.i2c | 32 sure that the other side doesn't want it also. A detailed explanation is best
|