Searched refs:BAD (Results 1 – 10 of 10) sorted by relevance
375 state->mode = BAD; in zlib_inflate()380 state->mode = BAD; in zlib_inflate()387 state->mode = BAD; in zlib_inflate()431 state->mode = BAD; in zlib_inflate()440 state->mode = BAD; in zlib_inflate()473 state->mode = BAD; in zlib_inflate()494 state->mode = BAD; in zlib_inflate()517 state->mode = BAD; in zlib_inflate()540 state->mode = BAD; in zlib_inflate()549 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
50 + BAD(54 + BAD(
113 /* BAD BAD BAD - get is after the handoff */
286 things will happen if a notifier in path sent a BAD notify code.
68 #define BAD 0xbad macro334 bad_card = ((dev->base_addr != 0) && (dev->mem_end == BAD)); in ne_probe1()
109 your computer, you encount some *BAD* error like disk crash.
10 I DISCLAIM ALL RESPONSIBILITY FOR ANY POSSIBLE BAD EFFECTS OF THIS CODE!
317 Anything less than 0xA0000 is, well, a BAD idea since it isn't above