Searched refs:NEVER (Results 1 – 13 of 13) sorted by relevance
40 ; NEVER REMOVE THE FOLLOWING REFERENCE FOR NETRNDIS.INF
212 NEVER SLEEP IN A COMPLETION HANDLER. These are often called in atomic
219 #define NEVER (0x7FFFFFFF) macro
52 3 = clock output is NEVER disabled
660 THEY NEVER DO ! while (NCR5380_read(C400_CONTROL_STATUS_REG) & CSR_53C80_REG); in NCR5380_pwrite()
31 It will ideally NEVER stop ticking as long as the system is running. It
31 NEVER OMIT SCHEDULING-CLOCK TICKS
172 NEVER = 0, enumerator
45 Newly written code should NEVER need this option but do
340 Maybe there are other cases too, but the rule should basically be to NEVER446 Comments are good, but there is also a danger of over-commenting. NEVER
302 that you should NEVER mess with the "done" field of a message, that is
317 appear in a filesystem. A subsystem is NEVER to touch the filesystem
265 should NEVER idly tamper with it. See Ralf Brown's interrupt list