Home
last modified time | relevance | path

Searched full:seemingly (Results 1 – 25 of 41) sorted by relevance

12

/linux-6.8/Documentation/userspace-api/media/mediactl/
Dmedia-controller-intro.rst25 between seemingly unrelated devices.
/linux-6.8/arch/hexagon/kernel/
Dvmlinux.lds.S21 See asm-generic/sections.h for seemingly required labels.
/linux-6.8/tools/testing/selftests/drivers/net/mlxsw/
Dqos_lib.sh30 # seemingly winning bandwidth on account of UC. Demand at least 2Gbps
/linux-6.8/arch/mips/include/asm/
Dcompiler.h20 * seemingly random behaviour, such as invalid memory accesses from incorrectly
/linux-6.8/arch/arc/include/asm/
Datomic-spinlock.h19 * Thus atomic_set() despite being 1 insn (and seemingly atomic) in arch_atomic_set()
/linux-6.8/include/linux/
Drcu_node_tree.h11 * This seemingly RCU-private file must be available to SRCU users
Drcu_segcblist.h5 * This seemingly RCU-private file must be available to SRCU users
Dfortify-string.h618 * - the size of ptr's object (seemingly by design, gcc & clang fail):
/linux-6.8/drivers/video/backlight/
Djornada720_bl.c128 * you will get seemingly non-related errors when in jornada_bl_probe()
/linux-6.8/Documentation/devicetree/bindings/pinctrl/
Dfsl,mxs-pinctrl.txt20 information about pull-up. For this reason, even seemingly boolean values are
Dnvidia,tegra124-xusb-padctl.txt48 what function the pins are assigned to. For this reason even seemingly boolean
Dnvidia,tegra-pinmux-common.yaml34 reason, even seemingly boolean values are actually tristates in this
/linux-6.8/arch/arm64/boot/dts/qcom/
Dmsm8916-samsung-gt5-common.dtsi125 * device tree, otherwise audio will seemingly play fine on the wrong SD line
Dmsm8916-samsung-a2015-common.dtsi264 * device tree, otherwise audio will seemingly play fine on the wrong SD line
Dmsm8939-samsung-a7.dts329 * device tree, otherwise audio will seemingly play fine on the wrong SD line
/linux-6.8/Documentation/process/
Dcve.rst41 explains the seemingly large number of CVEs that are issued by the Linux
D6.Followthrough.rst54 - Be prepared for seemingly silly requests for coding style changes
/linux-6.8/arch/hexagon/mm/
Dinit.c225 * The bootmem allocator seemingly just lives to feed memory in setup_arch_memory()
/linux-6.8/drivers/media/usb/dvb-usb/
Ddibusb-common.c271 /* additional keys TwinHan VisionPlus, the Artec seemingly not have */
/linux-6.8/drivers/regulator/
Dirq_helpers.c138 * Things have been seemingly successful => zero retry-counter. in regulator_notifier_isr_work()
/linux-6.8/Documentation/power/
Dfreezing-of-tasks.rst212 at this point. So, seemingly, the failure is due to the freezing of tasks.
/linux-6.8/drivers/input/mouse/
Dbyd.c364 /* The touchpad should reply with 4 seemingly-random bytes */ in byd_reset_touchpad()
/linux-6.8/sound/pci/
Dazt3328.h148 * seemingly random value). Hmm, possibly this is a register which
/linux-6.8/arch/x86/platform/intel-quark/
Dimr.c531 * the boot-time IMRs torn down or you'll find seemingly random resets when
/linux-6.8/drivers/firmware/arm_scmi/
Dvirtio.c661 * we have 'seemingly' emptied the virtqueue; if some buffers are still pending

12