Searched full:behaving (Results 1 – 23 of 23) sorted by relevance
69 Some PMUs are capable of behaving as an interrupt controller (mostly
96 * will fail. This is a stop gap measure to limit the badly behaving
21 * in response to this driver "mis-behaving" on his machine.
106 * DROPMASTER ioctl, which e.g. logind can call to force a non-behaving
24 /* Is device behaving sane? */
278 to coerce it into behaving.
74 in plain English for the reviewer to verify that the code is behaving
285 * the clock unit control register is behaving in the same in npcm7xx_fan_start_capture()
586 * It returns empty tokens, too, behaving exactly like the libc function
276 * memory, effectively behaving just like /dev/zero in pci_mmap_legacy_page_range()
1367 * undefined so behaving like if the pmd was none is safe (because it
51 * close the subflow with a RST, as it is not behaving as negotiated. in mptcp_parse_option()
326 * false positives but this did not break correctly behaving devices
676 * behaving just like /dev/zero in pci_mmap_legacy_page_range()
82 * task. If the task is behaving as a VMM, then this is will be managed by
953 /* There are two versions of YAS537 behaving differently */ in yas537_get_calibration_data()
177 /* Is device behaving sane? */
2660 the APM BIOS as a measure to lessen the effects of a badly behaving
1784 * a well behaving guest driver, it is not expected to allow in handle_ctrl_mq()
1457 /* aman@sgi.com - account for badly behaving firmware/NIC: in ace_init()
53 /* bulk DMA seems to be behaving for both IN and OUT */
3748 * behaving the way we expect it to. in smack_from_secattr()
4844 * well-behaving guests: They have to keep IRQs disabled at in vmx_inject_nmi()
