Home
last modified time | relevance | path

Searched full:wildly (Results 1 – 15 of 15) sorted by relevance

/linux/Documentation/devicetree/bindings/leds/
H A Dqcom,pm8058-led.yaml15 because sometimes these LED drivers are used for wildly different things than
/linux/include/uapi/linux/
H A Dlp.h67 * are wildly different...
/linux/Documentation/input/
H A Dinput.rst198 However, because the devices vary wildly, you might happen to have a
/linux/drivers/net/ethernet/intel/igc/
H A Digc_base.c305 * because the symbol error count will increment wildly if there in igc_init_hw_base()
/linux/Documentation/admin-guide/
H A Dsvga.rst97 what happens then. The screen will be probably flashing wildly for some time and
/linux/Documentation/networking/
H A Deql.rst203 up of the driver was tuned to handle slaves with wildly different
/linux/arch/x86/kvm/vmx/
H A Dpmu_intel.c26 * Perf's "BASE" is wildly misleading, architectural PMUs use bits 31:16 of ECX
/linux/arch/m68k/mac/
H A Dconfig.c163 * on hardware pages present on the Mac web site. Possibly wildly
/linux/drivers/net/ethernet/intel/e1000e/
H A D80003es2lan.c822 * because the symbol error count will increment wildly if there in e1000_init_hw_80003es2lan()
H A D82571.c1129 * because the symbol error count will increment wildly if there in e1000_init_hw_82571()
H A Dich8lan.c5032 * because the symbol error count will increment wildly if there in e1000_init_hw_ich8lan()
/linux/drivers/input/mouse/
H A Dpsmouse-base.c216 * Without this bit of weirdness moving up gives wildly in psmouse_process_byte()
/linux/drivers/char/xillybus/
H A Dxillyusb.c2110 * Except for wildly misbehaving hardware, or if it was disconnected in xillyusb_discovery()
/linux/Documentation/filesystems/xfs/
H A Dxfs-online-fsck-design.rst295 reservation step due to wildly incorrect summary counters.
/linux/kernel/sched/
H A Dcore.c2760 * This function is wildly self concurrent; here be dragons.