Searched full:complexities (Results 1 – 20 of 20) sorted by relevance
41 # systemd complexities with Conflicts statements between the targets to
17 logical volumes on top of MTD devices, hides some complexities of
104 /* ignore cache complexities for now */ in _start()
55 * those extra complexities for calculating multiplier etc could completely
7 logical volumes on top of MTD devices, hides some complexities of
44 There are a few complexities here. The different x86-64 entries
15 systems, do not require driver support for complexities such as regulator
517 There are a number of additional complexities introduced when one wants
119 * However, there are some complexities to the scheme.
746 * to some complexities. That should be fixed up at some
1945 logical volumes on top of MTD devices, hides some complexities of
136 | two independent pieces of roughly equal complexities
1422 * To avoid recursion complexities, directories aren't supported for now.
947 * stream from the driver layer. Handles the complexities of UTF-8 multibyte
1084 * There are complexities surrounding how we determine the timestamps we in joycon_parse_imu_report()
1703 * relocating (due to the complexities in lock handling), in eb_copy_relocations()
1250 To handle all these complexities, BitBake runs in two phases. The first
4614 * avoid having to deal with PDPTEs and other complexities. in fast_pgd_switch()
6794 # two independent pieces of roughly equal complexities #
6900 # two independent pieces of roughly equal complexities #