Searched refs:BAD (Results 1 – 14 of 14) 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(
139 BAD = -1, enumerator158 return BAD; in kyber_lat_status()203 case BAD: in kyber_adjust_rw_depth()250 case BAD: in kyber_adjust_other_depth()
139 /* BAD BAD BAD - get is after the handoff */
69 start with ``git bisect start [BAD] [GOOD]``
67 #define BAD 0xbad macro339 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!
973 /* THIS CODE BAD BAD BAD BAD: IF IT WAS ANY WORSE IT WOULD USE
995 /* THIS CODE BAD BAD BAD BAD: IF IT WAS ANY WORSE IT WOULD USE
1261 MODE_STATUS(BAD),
317 Anything less than 0xA0000 is, well, a BAD idea since it isn't above
