/openbmc/linux/Documentation/userspace-api/media/mediactl/ |
H A D | media-controller-intro.rst | 25 between seemingly unrelated devices.
|
/openbmc/linux/tools/testing/selftests/drivers/net/mlxsw/ |
H A D | qos_lib.sh | 30 # seemingly winning bandwidth on account of UC. Demand at least 2Gbps
|
/openbmc/openbmc/poky/documentation/profile-manual/ |
H A D | arch.rst | 13 is, however, that in recent years this seemingly disparate set of tools
|
/openbmc/linux/arch/hexagon/kernel/ |
H A D | vmlinux.lds.S | 21 See asm-generic/sections.h for seemingly required labels.
|
/openbmc/u-boot/drivers/mmc/ |
H A D | bcmstb_sdhci.c | 21 * actually running at 100 MHz (seemingly without issue), which is
|
/openbmc/linux/arch/mips/include/asm/ |
H A D | compiler.h | 20 * seemingly random behaviour, such as invalid memory accesses from incorrectly
|
/openbmc/linux/arch/arc/include/asm/ |
H A D | atomic-spinlock.h | 19 * Thus atomic_set() despite being 1 insn (and seemingly atomic) in arch_atomic_set()
|
/openbmc/linux/include/linux/ |
H A D | rcu_node_tree.h | 11 * This seemingly RCU-private file must be available to SRCU users
|
H A D | rcu_segcblist.h | 5 * This seemingly RCU-private file must be available to SRCU users
|
/openbmc/linux/drivers/video/backlight/ |
H A D | jornada720_bl.c | 128 * you will get seemingly non-related errors when in jornada_bl_probe()
|
/openbmc/u-boot/common/init/ |
H A D | board_init.c | 96 * (seemingly useless) incrementation causes no code increase.
|
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
H A D | fsl,mxs-pinctrl.txt | 20 information about pull-up. For this reason, even seemingly boolean values are
|
H A D | nvidia,tegra124-xusb-padctl.txt | 48 what function the pins are assigned to. For this reason even seemingly boolean
|
H A D | nvidia,tegra-pinmux-common.yaml | 34 reason, even seemingly boolean values are actually tristates in this
|
/openbmc/witherspoon-pfault-analysis/power-supply/ |
H A D | record_manager.cpp | 63 // need to clear. If we see a 0 seemingly out of nowhere, in add()
|
/openbmc/phosphor-power/power-supply/ |
H A D | record_manager.cpp | 63 // need to clear. If we see a 0 seemingly out of nowhere, in add()
|
/openbmc/linux/arch/hexagon/mm/ |
H A D | init.c | 224 * The bootmem allocator seemingly just lives to feed memory in setup_arch_memory()
|
/openbmc/linux/drivers/media/usb/dvb-usb/ |
H A D | dibusb-common.c | 271 /* additional keys TwinHan VisionPlus, the Artec seemingly not have */
|
/openbmc/linux/Documentation/process/ |
H A D | 6.Followthrough.rst | 54 - Be prepared for seemingly silly requests for coding style changes
|
/openbmc/linux/drivers/regulator/ |
H A D | irq_helpers.c | 138 * Things have been seemingly successful => zero retry-counter. in regulator_notifier_isr_work()
|
/openbmc/linux/Documentation/power/ |
H A D | freezing-of-tasks.rst | 201 at this point. So, seemingly, the failure is due to the freezing of tasks.
|
/openbmc/linux/drivers/input/mouse/ |
H A D | byd.c | 364 /* The touchpad should reply with 4 seemingly-random bytes */ in byd_reset_touchpad()
|
/openbmc/linux/sound/pci/ |
H A D | azt3328.h | 148 * seemingly random value). Hmm, possibly this is a register which
|
/openbmc/openbmc/poky/documentation/overview-manual/ |
H A D | yp-intro.rst | 404 commands in an environment that seemingly has root privileges. 861 of several BitBake variables that are seemingly mis-named, (e.g.
|
/openbmc/linux/arch/x86/platform/intel-quark/ |
H A D | imr.c | 531 * the boot-time IMRs torn down or you'll find seemingly random resets when
|