Home
last modified time | relevance | path

Searched refs:BAD (Results 1 – 11 of 11) sorted by relevance

/linux-4.1.27/lib/zlib_inflate/
Dinflate.c360 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 …]
Dinffast.c194 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()
Dinflate.h43 BAD, /* got a data error -- remain here until reset */ enumerator
/linux-4.1.27/scripts/coccinelle/iterators/
Ditnull.cocci54 + BAD(
58 + BAD(
/linux-4.1.27/Documentation/
Dkref.txt113 /* BAD BAD BAD - get is after the handoff */
Dcpu-hotplug.txt310 things will happen if a notifier in path sent a BAD notify code.
/linux-4.1.27/drivers/net/ethernet/8390/
Dne.c67 #define BAD 0xbad macro
342 bad_card = ((dev->base_addr != 0) && (dev->mem_end == BAD)); in ne_probe1()
/linux-4.1.27/Documentation/filesystems/
Dbefs.txt10 I DISCLAIM ALL RESPONSIBILITY FOR ANY POSSIBLE BAD EFFECTS OF THIS CODE!
/linux-4.1.27/Documentation/scsi/
DNinjaSCSI.txt109 your computer, you encount some *BAD* error like disk crash.
/linux-4.1.27/drivers/gpu/drm/
Ddrm_modes.c1060 MODE_STATUS(BAD),
/linux-4.1.27/Documentation/networking/
Darcnet-hardware.txt317 Anything less than 0xA0000 is, well, a BAD idea since it isn't above