Searched full:involve (Results 1 – 25 of 247) sorted by relevance
12345678910
7 # Some lio_test testcases involve system resource limitations, so cannot run concurrently
190 * Relaxed register read/write functions don't involve cpu instructions that205 * Relaxed register read/write functions don't involve cpu instructions that220 * Relaxed register read/write functions don't involve cpu instructions that
5 # large source trees that involve several nested make calls.
18 /// involve AST nodes.
19 sub-nodes that involve the codec. The codec uses one 8bit time-slot per
19 that involve the codec. The codec uses one 8bit time-slot per channel.
15 # doesn't involve ld.so traversing the filesystem).
134 Mounting a filesystem with write access on a card write protected may involve a kernel crash.
56 * would involve some form of synchronization between the vcpus to vmclear
71 For devices that involve the host to transmit each
200 Many operations on the tree involve traversing linked lists.
243 All operations on contexts involve linked list traversal.
179 * operation itself does not involve "directory" permissions.181 * operation does not involve anything *but* a directory. This
16 every recognized option symbol. Then adding a new tag would involve
61 will involve a resident key. User verification may be requested
25 // involve generating C++ code to the provided raw_ostream.
46 scanning process involve any encryption.
56 * involve a callback being invoked more than once not only to convert to
42 Functions that involve attributes that have reference counts themselves,
66 // The expansion may involve new basic blocks. in runImpl()
57 network" function, as such a function would involve the creation of
63 # some of the rules involve .h sources, so remove them from mkdep line
140 # some targets involve old pre-built targets
37 * Translation could potentially involve the following
211 As an example that does not involve numbers,