Searched full:behave (Results 1 – 25 of 499) sorted by relevance
12345678910>>...20
9 * mapping is special. At first it behave as file, but after write anything10 * it behave as anon. This test is intent to test such case.
10 files on them, i.e. MSDOS files will look and behave just like all48 transparent, i.e. the MSDOS files look and behave just like all
12 files on them, i.e. MSDOS files will look and behave just like all50 transparent, i.e. the MSDOS files look and behave just like all
45 source (The port will behave as source only DFP port)46 sink (The port will behave as sink only UFP port)47 dual (The port will behave as dual-role-data and
42 /* refcount_add() should behave just like refcount_inc() above. */60 /* refcount_inc_not_zero() should behave just like refcount_inc() above. */72 /* refcount_add_not_zero() should behave just like refcount_inc() above. */
32 # Make it behave more like gcc by erroring when these flags are encountered
19 write functions behave a bit differently because the message formats
28 1: All I/Os behave as configured
11 * bits from a sysfs handle in order to determine how to behave. */
15 it to behave as a hwmon IC. There are many different revisions of the
11 STDP2690 behave as the stock bridges would. The compatible strings include the
52 unsigned int lns_mode:1; /* behave as LNS?98 unsigned int lns_mode:1; /* behave as LNS?
85 behave quite right at the moment.146 transaction translators are in use; some drivers have been seen to behave
43 - Validate that all filesystems behave properly.
6 * blackhole_dev and expects kernel to behave in a sane manner