| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-bdi | 38 total write-back cache that relates to its current average
52 total write-back cache that relates to its current average
93 total write-back cache that relates to its current average
|
| /openbmc/linux/include/linux/ |
| H A D | nvme-tcp.h | 156 * @command_id: nvme command identifier which this relates to
174 * @command_id: nvme command identifier which this relates to
|
| /openbmc/linux/drivers/iommu/iommufd/ |
| H A D | Kconfig | 10 it relates to managing IO page tables that point at user space memory.
|
| /openbmc/linux/Documentation/devicetree/bindings/media/xilinx/ |
| H A D | video.txt | 22 Video IP and System Design Guide" [UG934]. How the format relates to the IP
|
| /openbmc/linux/Documentation/devicetree/bindings/iio/ |
| H A D | mount-matrix.txt | 40 Another frame of reference is how the device with its sensor relates to the
44 becomes identical and we can focus on the data as it relates to the surrounding
|
| /openbmc/qemu/migration/ |
| H A D | dirtyrate.h | 35 * Lower limit relates to the smallest realistic downtime it
|
| /openbmc/linux/Documentation/driver-api/media/ |
| H A D | v4l2-intro.rst | 53 This is a rough schematic of how it all relates:
|
| /openbmc/linux/arch/alpha/kernel/ |
| H A D | sys_eb64p.c | 167 * above for PCI interrupts. The IRQ relates to which bit the interrupt
|
| H A D | sys_mikasa.c | 144 * above for PCI interrupts. The IRQ relates to which bit the interrupt
|
| H A D | sys_alcor.c | 181 * above for PCI interrupts. The IRQ relates to which bit the interrupt
|
| H A D | sys_noritake.c | 192 * above for PCI interrupts. The IRQ relates to which bit the interrupt
|
| H A D | sys_miata.c | 150 * above for PCI interrupts. The IRQ relates to which bit the interrupt
|
| /openbmc/linux/Documentation/driver-api/80211/ |
| H A D | mac80211-advanced.rst | 164 how it relates to mac80211 and drivers.
|
| /openbmc/docs/designs/ |
| H A D | error-log-handling-for-phal.md | 25 operation. Callout points to a specific hardware with in the server that relates
|
| /openbmc/linux/Documentation/mm/ |
| H A D | memory-model.rst | 141 address ranges. The "device" aspect of `ZONE_DEVICE` relates to the fact
|
| /openbmc/linux/Documentation/userspace-api/ |
| H A D | iommufd.rst | 13 IOMMUFD is the user API to control the IOMMU subsystem as it relates to managing
|
| /openbmc/linux/drivers/watchdog/ |
| H A D | imgpdc_wdt.c | 25 * The following table shows how the user-configured timeout relates
|
| /openbmc/ibm-logging/ |
| H A D | manager.hpp | 240 * relates to the main ...logging/entry/X object but has a different path.
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | kernel-parameters.rst | 191 BUGS= Relates to possible processor bugs on the said processor.
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | OLFL-1.3 | 91 The foregoing right of use relates to the Subject Matter of the License, in
|
| /openbmc/linux/Documentation/trace/coresight/ |
| H A D | coresight-config.rst | 124 has a feature that relates to the currently active configuration.
|
| /openbmc/linux/drivers/cpufreq/ |
| H A D | cpufreq-nforce2.c | 245 * @relation: how that frequency relates to achieved frequency
|
| /openbmc/docs/security/ |
| H A D | obmc-security-response-team-guidelines.md | 86 and reference it in the commit message, stating how the fix relates to the CVE.
|
| /openbmc/linux/Documentation/devicetree/bindings/regulator/ |
| H A D | regulator.yaml | 222 in microvolts, each value in the array relates to the corresponding
|
| /openbmc/phosphor-networkd/src/ |
| H A D | ncsi_cmd.cpp | 343 * For output that relates to command-line usage, we just output directly to
|