Searched full:behave (Results 1 – 25 of 227) sorted by relevance
12345678910
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
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. */
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
19 write functions behave a bit differently because the message formats
11 STDP2690 behave as the stock bridges would. The compatible strings include the
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
19 it to behave as a hwmon IC. There are many different revisions of the
68 * cleanup. For clarity, running tests in a test suite would behave as follows:
43 - Validate that all filesystems behave properly.
6 * blackhole_dev and expects kernel to behave in a sane manner
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
62 that the Slave might behave in implementation-defined ways. The bus
104 ** these functions, they behave exactly like the amiga os routines
295 * 486 CPUs did not behave this way. in ffs()336 * 486 CPUs did not behave this way. in fls()
5 // Test that out-of-bounds reads/writes behave as expected.
21 * it will behave like a fixed regulator.
79 behave like most of new OSS/Free drivers in 2.4/2.6 kernels.
31 rtnl_link_ops, where children created using either way behave the same.
83 PHY_INTERFACE_MODE_RGMII, by default, does not behave as RGMII with no
44 * nonstandard and doesn't really behave like an HID report. in a4_input_mapping()
32 these instructions behave as NOPs. Applications and libraries using
125 This backend makes Linux behave like an I2C EEPROM. Please read