/openbmc/linux/Documentation/devicetree/bindings/leds/ |
H A D | qcom,pm8058-led.yaml | 15 because sometimes these LED drivers are used for wildly different things than
|
/openbmc/linux/include/uapi/linux/ |
H A D | lp.h | 67 * are wildly different...
|
/openbmc/linux/arch/x86/lib/ |
H A D | delay.c | 10 * depends wildly on alignment on many x86 processors. The additional
|
/openbmc/linux/drivers/net/ethernet/natsemi/ |
H A D | macsonic.c | 289 /* Danger! My arms are flailing wildly! You *must* set lp->reg_offset in mac_onboard_sonic_probe() 454 /* Danger! My arms are flailing wildly! You *must* set lp->reg_offset in mac_sonic_nubus_probe_board()
|
/openbmc/linux/Documentation/input/ |
H A D | input.rst | 198 However, because the devices vary wildly, you might happen to have a
|
/openbmc/linux/drivers/net/ethernet/intel/igc/ |
H A D | igc_base.c | 305 * because the symbol error count will increment wildly if there in igc_init_hw_base()
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | svga.rst | 97 what happens then. The screen will be probably flashing wildly for some time and
|
/openbmc/linux/Documentation/networking/ |
H A D | eql.rst | 203 up of the driver was tuned to handle slaves with wildly different
|
/openbmc/linux/arch/m68k/mac/ |
H A D | config.c | 173 * on hardware pages present on the Mac web site. Possibly wildly
|
/openbmc/linux/drivers/net/ethernet/intel/e1000e/ |
H A D | 80003es2lan.c | 822 * because the symbol error count will increment wildly if there in e1000_init_hw_80003es2lan()
|
H A D | 82571.c | 1129 * because the symbol error count will increment wildly if there in e1000_init_hw_82571()
|
H A D | ich8lan.c | 5030 * because the symbol error count will increment wildly if there in e1000_init_hw_ich8lan()
|
/openbmc/linux/drivers/net/wireless/intersil/orinoco/ |
H A D | hw.c | 185 "Wildly guessing capabilities...\n", err); in determine_fw_capabilities()
|
/openbmc/linux/kernel/time/ |
H A D | posix-timers.c | 1195 * wildly and even change during runtime when the underlying devices are
|
/openbmc/qemu/system/ |
H A D | physmem.c | 236 /* Wildly overreserve - it doesn't matter much. */ in phys_page_set() 379 * regions overlap wildly. For this reason we cannot clamp the accesses in address_space_translate_internal()
|
/openbmc/linux/drivers/input/mouse/ |
H A D | psmouse-base.c | 216 * Without this bit of weirdness moving up gives wildly in psmouse_process_byte()
|
/openbmc/linux/drivers/char/xillybus/ |
H A D | xillyusb.c | 2110 * Except for wildly misbehaving hardware, or if it was disconnected in xillyusb_discovery()
|
/openbmc/linux/drivers/clk/renesas/ |
H A D | r9a06g032-clocks.c | 995 * that is 16 times the baud rate -- and that is wildly outside the in r9a06g032_div_determine_rate()
|
/openbmc/linux/tools/lib/bpf/ |
H A D | btf_dump.c | 1258 * have also wildly different syntax and how nesting of them are done. See
|
/openbmc/linux/drivers/net/ethernet/intel/igb/ |
H A D | e1000_82575.c | 1551 * because the symbol error count will increment wildly if there in igb_init_hw_82575()
|
/openbmc/linux/drivers/infiniband/sw/rdmavt/ |
H A D | qp.c | 148 /* reject a wildly large period */ in rvt_wss_init()
|
/openbmc/linux/drivers/net/ethernet/intel/e1000/ |
H A D | e1000_hw.c | 621 * because the symbol error count will increment wildly if there in e1000_init_hw()
|
/openbmc/linux/Documentation/filesystems/ |
H A D | xfs-online-fsck-design.rst | 295 reservation step due to wildly incorrect summary counters.
|
/openbmc/linux/kernel/sched/ |
H A D | core.c | 2887 * This function is wildly self concurrent; here be dragons.
|