Searched full:consequences (Results 1 – 25 of 59) sorted by relevance
123
11 - Errors in regulator configuration can have very serious consequences
24 can live with the consequences, this property can be used to enable
41 SOME OF WHICH MAY HAVE SERIOUS CONSEQUENCES. CARNEGIE MELLON ALLOWS
278 the consequences).
145 * incorrect, grep kernel sources and think about consequences
55 time_. This is a big hammer, and has some unfortunate consequences: inablity
48 Consequences for users
91 Say N unless you fully understand the consequences.
29 The consequences are that I won't guarantee the correctness of
122 * atomic sequence numbers is slower though, and the consequences of racing are
126 * and the consequences later is quite hard to detect what the actual in xen_remap_domain_gfn_array()
19 Interrupt Enable Register while in operation. The consequences are
165 block degradation, but high enough to avoid the consequences of
187 of RAM into your 32-bit machine. This has a number of consequences:
240 to the process and leads to the consequences already explained.
223 constraint has negative consequences. EXPORT_OP_REMOTE_FS enables
223 to a number of negative consequences, most of them quite catastrophic.
64 * This check was put in to avoid "unpleasant" consequences if in ath5k_pci_read_cachesize()
165 This rule does have less-obvious consequences so it is worth working
329 (along with any consequences of those changes). If a payload is provided
240 * file. This has consequences for in gfs2_write_jdata_batch()
256 Taken all together there's two consequences for the atomic design:
340 But doing so has some unintended consequences.