Searched full:complication (Results 1 – 20 of 20) sorted by relevance
64 Now, there's a secondary complication: there's a cheap way to test
460 complication is when the ring buffer wraps. */501 The only potential complication is that the address register is shared
40 * says: a lot of complication here is taken away because:
35 * In XE we avoid all of this complication by not allowing a BO list to be
322 that mention "leftovers" in some way are related to this complication.
220 in the sysfs hierarchy, and not have to mess with the whole complication of
527 * avoid too much complication, it will restart the whole fault at level
331 * involves added complication. We need to walk before in br2684_start_xmit()
361 * deferred event handling complication. in dw8250_clk_notifier_cb()
593 * output as much as possible, but there is a bit of a complication. in tnum_strn()
569 * complication of a bit setting for a specific index having different settings570 * in different nodes. This would then introduce the further complication
1465 * necessary to add the complication in the emulation currently. Reject in mock_set_test_feature()
402 * additional complication which comes from C rules. The main idea for C is
3491 * Additional complication we need to keep in mind comes from the fact that
1818 * complication is that we need to start a commit operation if the
3614 * only complication is having to make sure that initialization in tdx_bringup()
2202 * avoid this complication, by simply interpreting a list of folios as a list of
2558 * little complication since the state of a new directory is a in ocfs2_fill_new_dir_dx()
3370 * As an additional complication, if userspace was compiled with
2604 * unnecessary complication, it is actually inevitable in blocksize < pagesize