Searched full:behaving (Results 1 – 24 of 24) sorted by relevance
44 // stop behaving like NaggyMock<MockFoo> and start behaving like
70 Some PMUs are capable of behaving as an interrupt controller (mostly
31 # avoid the targets behaving differently
62 * under Windows, such an fflush is documented as behaving instead in fflush()
97 Some PMUs are capable of behaving as an interrupt controller (mostly
61 either behaving as if the filter were not present
546 * of each ring. The reason is this: If the user is behaving correctly, in netmap_pipe_krings_delete_both()548 * some ring. If the user is not behaving correctly, we cannot release in netmap_pipe_krings_delete_both()
287 * behaving as a LIFO (and insertion/removal is therefore \
170 to verify ZFS is behaving as intended.
433 functions that result in the file-type behaving as the system stdio443 functions that result in the file-type behaving as the system stdio
110 /// behaving as if elements were added one at a time with `add`.
247 in little-endian format instead of behaving like `memcmp()`.
1316 is used to terminate programs which are behaving unreasonably.
412 * interoperability issues with incorrectly behaving authentication
1516 # interoperability issues with incorrectly behaving authentication servers.
508 * add a workaround for incorrectly behaving APs that try to use
1572 other packets, we're typically behaving like a well behaved2818 enabled bridging so the network is behaving perfectly nor-
884 * It's better to catch this pathological case early than behaving in g_part_gpt_probe()
1820 * If there are any terminals behaving different way, it would be
1747 * to learn that the compiler is behaving badly very quickly.
1110 When you find your makefile isn't behaving as you hoped, the first
1164 When you find your makefile isn't behaving as you hoped, the first
2158 so that you can see if your script is behaving as you expect.
42778 prim-behaving