Searched refs:BAD (Results 1 – 11 of 11) sorted by relevance
360 state->mode = BAD; in zlib_inflate()365 state->mode = BAD; in zlib_inflate()372 state->mode = BAD; in zlib_inflate()416 state->mode = BAD; in zlib_inflate()425 state->mode = BAD; in zlib_inflate()458 state->mode = BAD; in zlib_inflate()479 state->mode = BAD; in zlib_inflate()502 state->mode = BAD; in zlib_inflate()525 state->mode = BAD; in zlib_inflate()534 if (state->mode == BAD) break; in zlib_inflate()[all …]
194 state->mode = BAD; in inflate_fast()205 state->mode = BAD; in inflate_fast()313 state->mode = BAD; in inflate_fast()327 state->mode = BAD; in inflate_fast()
43 BAD, /* got a data error -- remain here until reset */ enumerator
54 + BAD(58 + BAD(
113 /* BAD BAD BAD - get is after the handoff */
310 things will happen if a notifier in path sent a BAD notify code.
67 #define BAD 0xbad macro342 bad_card = ((dev->base_addr != 0) && (dev->mem_end == BAD)); in ne_probe1()
10 I DISCLAIM ALL RESPONSIBILITY FOR ANY POSSIBLE BAD EFFECTS OF THIS CODE!
109 your computer, you encount some *BAD* error like disk crash.
1060 MODE_STATUS(BAD),
317 Anything less than 0xA0000 is, well, a BAD idea since it isn't above