Home
last modified time | relevance | path

Searched full:behaving (Results 1 – 25 of 27) sorted by relevance

12

/openbmc/linux/drivers/gpu/drm/i915/
H A Di915_file_private.h96 * will fail. This is a stop gap measure to limit the badly behaving
/openbmc/linux/Documentation/devicetree/bindings/soc/samsung/
H A Dexynos-pmu.yaml87 Some PMUs are capable of behaving as an interrupt controller (mostly
/openbmc/linux/drivers/scsi/
H A Dppa.h21 * in response to this driver "mis-behaving" on his machine.
/openbmc/linux/include/drm/
H A Ddrm_ioctl.h106 * DROPMASTER ioctl, which e.g. logind can call to force a non-behaving
/openbmc/linux/drivers/xen/
H A Dgrant-dma-ops.c25 /* Is device behaving sane? */
/openbmc/linux/Documentation/process/
H A Demail-clients.rst278 to coerce it into behaving.
H A Dsubmitting-patches.rst74 in plain English for the reviewer to verify that the code is behaving
/openbmc/qemu/hw/arm/
H A Dversatilepb.c202 * Refuse to run rather than behaving very confusingly. in versatile_init()
/openbmc/u-boot/lib/
H A Dstring.c413 * It returns empty tokens, too, behaving exactly like the libc function
/openbmc/linux/lib/
H A Dstring.c502 * It returns empty tokens, too, behaving exactly like the libc function
/openbmc/linux/drivers/hwmon/
H A Dnpcm750-pwm-fan.c290 * the clock unit control register is behaving in the same in npcm7xx_fan_start_capture()
/openbmc/openbmc/poky/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/
H A Dwpa_supplicant.conf419 # interoperability issues with incorrectly behaving authentication servers.
/openbmc/openbmc/poky/documentation/ref-manual/
H A Ddevtool-reference.rst537 behaving as expected. When both of the following conditions are met, your
/openbmc/u-boot/doc/driver-model/
H A DREADME.txt598 parent device which is a bus, causes the device to start behaving like a
/openbmc/linux/arch/powerpc/kernel/
H A Dpci-common.c676 * behaving just like /dev/zero in pci_mmap_legacy_page_range()
/openbmc/linux/net/mptcp/
H A Doptions.c56 * close the subflow with a RST, as it is not behaving as negotiated. in mptcp_parse_option()
/openbmc/linux/drivers/firewire/
H A Dsbp2.c327 * false positives but this did not break correctly behaving devices
/openbmc/linux/drivers/iio/magnetometer/
H A Dyamaha-yas530.c954 /* There are two versions of YAS537 behaving differently */ in yas537_get_calibration_data()
/openbmc/linux/arch/arm64/kernel/
H A Dfpsimd.c82 * task. If the task is behaving as a VMM, then this is will be managed by
/openbmc/linux/drivers/net/
H A Dxen-netfront.c177 /* Is device behaving sane? */
/openbmc/linux/arch/x86/
H A DKconfig2719 the APM BIOS as a measure to lessen the effects of a badly behaving
/openbmc/linux/drivers/net/ethernet/alteon/
H A Dacenic.c1457 /* aman@sgi.com - account for badly behaving firmware/NIC: in ace_init()
/openbmc/linux/drivers/vdpa/mlx5/net/
H A Dmlx5_vnet.c1940 * a well behaving guest driver, it is not expected to allow in handle_ctrl_mq()
/openbmc/linux/drivers/usb/gadget/udc/
H A Domap_udc.c53 /* bulk DMA seems to be behaving for both IN and OUT */
/openbmc/linux/security/smack/
H A Dsmack_lsm.c3906 * behaving the way we expect it to. in smack_from_secattr()

12