Home
last modified time | relevance | path

Searched refs:OK (Results 1 – 92 of 92) sorted by relevance

/linux-4.4.14/arch/powerpc/kernel/
Dprom_init_check.sh43 OK=0
47 OK=1
55 OK=1
58 OK=1
62 if [ $OK -eq 0 ]; then
/linux-4.4.14/drivers/net/plip/
Dplip.c346 #define OK 0 macro
375 if ((r = (*f)(nl->dev, nl, snd, rcv)) != OK && in plip_bh()
376 (r = plip_bh_timeout_error(nl->dev, nl, snd, rcv, r)) != OK) { in plip_bh()
436 return OK; in plip_bh_timeout_error()
477 return OK; in plip_none()
526 return OK; in plip_receive()
613 return OK; in plip_receive_packet()
687 return OK; in plip_receive_packet()
693 return OK; in plip_receive_packet()
696 return OK; in plip_receive_packet()
[all …]
/linux-4.4.14/Documentation/isdn/
DINTERFACE.fax105 OK message will be sent.
109 0: output OK message (more pages follow)
112 ISDN_TTY_FAX_TRAIN_OK output of +FDCS and OK message (for receive mode).
118 OK message, switching to phase E.
DHiSax.cert53 Only if the checksums are OK, and the signature of the file
DREADME.gigaset191 => OK or ERROR
194 => OK, CONNECT,
DREADME.HiSax335 Apr 13 21:01:59 kke01 kernel: Elsa: timer OK; resetting card
/linux-4.4.14/Documentation/power/
Dvideo.txt105 Asus L2400D s3_mode (3)(***) (S1 also works OK)
107 Asus L3800C (Radeon M7) s3_bios (2) (S1 also works OK)
111 Compaq Armada E500 - P3-700 none (1) (S1 also works OK)
131 HP Omnibook 5150 none (1), (S1 also works OK)
165 Toshiba Satellite 4030CDT s3_mode (3) (S1 also works OK)
166 Toshiba Satellite 4080XCDT s3_mode (3) (S1 also works OK)
/linux-4.4.14/drivers/net/fddi/skfp/h/
Dsba_def.h67 #define OK 0x01 /* ??????? */ macro
/linux-4.4.14/tools/build/tests/
Drun.sh69 echo OK
/linux-4.4.14/drivers/isdn/hardware/eicon/
Dpc_maint.h68 #define OK 0xff macro
Dmessage.c738 (*command_function)(Id, plci, OK); in start_internal_command()
764 (*(plci->internal_command_queue[0]))(Id, plci, OK); in next_internal_command()
3914 if ((rc == OK) && a->FlowControlSkipTable[ch]) { in callback()
4154 if (rc != OK) in control_rc()
4165 if (rc != OK) in control_rc()
4175 if (rc != OK) Info = _WRONG_STATE; in control_rc()
4186 || (!nl_rc && (req == CALL_REQ) && (rc != OK))) in control_rc()
4235 if (rc != OK) in control_rc()
4271 if (rc != OK) in control_rc()
4294 if (rc == OK) /* command supported, wait for indication */ in control_rc()
[all …]
Dpc.h268 #define OK 0xff /* command accepted */ macro
Ddi.c393 (Rc == OK)) { in isdn_rc()
463 if ((Rc != OK) || !a->FlowControlSkipTable[Ch]) in isdn_rc()
/linux-4.4.14/arch/s390/kvm/
DKconfig54 # OK, it's a little counter-intuitive to do this, but it puts it neatly under
/linux-4.4.14/arch/s390/net/
Dbpf_jit.S82 b OFF_OK(%r6) # Return OK
/linux-4.4.14/drivers/usb/usbip/
Dusbip_protocol.txt110 4 | 4 | 0x00000000 | Status: 0 for OK
195 4 | 4 | 0x00000000 | Status: 0 for OK
199 | | | device, if the previous status field was OK (0),
/linux-4.4.14/Documentation/usb/
Dacm.txt126 If all this seems to be OK, fire up minicom and set it to talk to the ttyACM
127 device and try typing 'at'. If it responds with 'OK', then everything is
Dgadget_printer.txt107 Printer OK
130 To set error status to printer OK:
426 printf(" Printer OK\n");
Dusbmon.txt206 char flag_data; /* 15: Same as text; Binary zero is OK. */
/linux-4.4.14/drivers/net/ethernet/sis/
Dsis900.h199 OK = 0x08000000, DSIZE = 0x00000FFF enumerator
/linux-4.4.14/tools/perf/tests/
Dmake277 @echo OK
280 @echo OK
/linux-4.4.14/Documentation/scsi/
Darcmsr_spec.txt9 ** (DRIVER DATA WRITE OK)
11 ** (DRIVER DATA READ OK)
13 ** (IOP331 DATA WRITE OK)
15 ** (IOP331 DATA READ OK)
Din2000.txt22 old as 2.1, so we'll assume that all cards are OK.
88 Kernel 1.3.70 interrupt mods added; old kernels still OK.
DChangeLog.ncr53c8xx491 as OK driver status.
Dncr53c8xx.txt130 This driver has been tested OK with linux/i386, Linux/Alpha and Linux/PPC.
DChangeLog.lpfc697 * Fix build on big endian machines: while #if was OK with
/linux-4.4.14/Documentation/blockdev/
DREADME.DAC960337 /proc/rd/status returns "OK" when all DAC960 controllers in the system are
446 OK
449 returns "OK" indicating that there are no problems with any DAC960 controller
467 /proc/rd/status has changed from "OK" to "ALERT":
580 OK
618 OK
621 returns "OK" indicating that there are no problems with any DAC960 controller
643 /proc/rd/status has changed from "OK" to "ALERT":
722 OK
Dfloppy.txt97 later are OK. You also need at least a 486 to use nodma.
/linux-4.4.14/arch/arm/boot/dts/
Dste-nomadik-nhk15.dts126 0x02030160 // OK
Dlogicpd-torpedo-som.dtsi105 * gpio157 is not connected. So this should be OK to keep common for now,
/linux-4.4.14/arch/x86/kvm/
DKconfig102 # OK, it's a little counter-intuitive to do this, but it puts it neatly under
/linux-4.4.14/drivers/scsi/
Deata_generic.h74 #define OK 0 macro
/linux-4.4.14/Documentation/devicetree/bindings/usb/
Ddwc3.txt24 - snps,u2ss_inp3_quirk: set if we enable P3 OK for U2/SS Inactive quirk
/linux-4.4.14/Documentation/
Dinit.txt4 OK, so you've got this pretty unintuitive message (currently located
Dsysrq.txt158 that the sync hasn't taken place until you see the "OK" and "Done" appear
160 OK or Done message...)
165 "OK" and "Done" message appear on the screen.
Dkernel-per-CPU-kthreads.txt84 be de-jittered. (It is OK to force this CPU offline and then
91 be de-jittered. (It is OK to force this CPU offline and then
98 be de-jittered. (It is OK to force this CPU offline and then
DSubmitChecklist51 static functions, but OK there also.) Use 'make htmldocs' or 'make
Dxz.txt74 size for in-kernel use (maybe more is OK for initramfs). The presets
Dbus-virt-phys-mapping.txt176 OK, that just about covers the basics of accessing IO portably. Questions?
Dapplying-patches.txt130 re-downloading the patch and if things are still not OK then you'd be advised
146 The resulting file may or may not be OK, depending on the reason the file
Dparport-lowlevel.txt662 0 handshake OK; IEEE 1284 peripheral and mode available
664 1 handshake OK; IEEE 1284 peripheral present but mode not
DCodingStyle357 different cases, it's OK to have a longer function.
496 That's OK, we all do. You've probably been told by your long-time Unix
DSubmittingPatches220 complete, that is OK. Simply note "this patch depends on patch X"
/linux-4.4.14/Documentation/networking/caif/
Dspi_porting.txt121 * called with the parameter assert set to true. It is OK
133 * to the CAIF SPI interface. It is OK to call this function
/linux-4.4.14/Documentation/networking/
Dnetdev-FAQ.txt152 the better the odds that it is an OK candidate for stable. So scrambling
197 use the mailing lists and not reach out directly. If you aren't OK with
210 Q: Any other tips to help ensure my net/net-next patch gets OK'd?
Dpktgen.txt62 Result: OK: add_device=eth4@0
108 Result: OK: 15430(c15405+d25) usec, 100000 (60byte,0frags)
Dvortex.txt359 - OK, it's a driver problem.
Dcs89x0.txt464 transmitted OK or in error. The test can be terminated anytime by the user at
Darcnet-hardware.txt357 ON ON Normal state - everything OK, nothing
/linux-4.4.14/Documentation/serial/
Dn_gsm.txt37 and check that it's successful (should return OK) */
/linux-4.4.14/lib/raid6/
Dint.uc77 vv = (vv << 1) - (vv >> 7); /* Overflow on the top bit is OK */
/linux-4.4.14/arch/um/
DKconfig.um91 be 1 << order pages. The default is OK unless you're running Valgrind
/linux-4.4.14/Documentation/DocBook/media/
Dbayer.png.b6454 0Y9zFe891tHZ/HHFMo5zEawV/uo4+HKsVWCdli1C+2F2p7nRj+OK+O7dUeRio7vnPdVoazIr3/Ru
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dab8500.txt39 : MAIN_EXT_CH_NOT_OK : : main charger not OK
/linux-4.4.14/Documentation/RCU/
DlistRCU.txt49 you are turning auditing off, it is OK to audit a few extra system calls.
312 is really OK to be processing stale data, then you don't need a
Drcu_dereference.txt125 However, comparisons are OK in the following cases:
Dtrace.txt103 well have qp=1, which is OK: RCU is still ignoring them.
DRTFP.txt350 values sometimes OK.
1264 is indefinite grace periods... But this is OK for experimentation
/linux-4.4.14/drivers/mtd/ubi/
DKconfig24 The default value should be OK for SLC NAND flashes, NOR flashes and
/linux-4.4.14/Documentation/misc-devices/
Dlis3lv02d49 Seltest returns either "OK x y z" or "FAIL x y z" where x, y and z are
/linux-4.4.14/arch/arm/kernel/
Dentry-header.S98 @ r8-r12 is OK.
/linux-4.4.14/Documentation/filesystems/
Dxfs-self-describing-metadata.txt179 is extensively verified and if it is OK we then update the LSN from the last
237 by checking the superblock of the feature bit, and then if the CRC verifies OK
322 modified in memory. If the metadata verifies OK, and CRCs are enabled, we then
Dhpfs.txt123 OK, I could implement complex codepage support to this driver but I think it
/linux-4.4.14/drivers/mtd/chips/
Dcfi_cmdset_0002.c963 map_word status, OK = CMD(0x80); in xip_udelay() local
996 } while (!map_word_andequal(map, status, OK, OK)); in xip_udelay()
1046 } while (!map_word_andequal(map, status, OK, OK) in xip_udelay()
Dcfi_cmdset_0001.c1112 map_word status, OK = CMD(0x80); in xip_wait_for_operation() local
1153 } while (!map_word_andequal(map, status, OK, OK)); in xip_wait_for_operation()
1211 } while (!map_word_andequal(map, status, OK, OK) in xip_wait_for_operation()
/linux-4.4.14/Documentation/sound/oss/
Dmwave9 OK, first thing - the IRQ problem IS a problem, whether the test is bypassed or
DREADME.OSS695 should work OK.
/linux-4.4.14/drivers/net/wireless/ath/ath9k/
Dhtc.h406 OK, /* no change needed */ enumerator
Dbeacon.c424 sc->beacon.updateslot = OK; in ath9k_beacon_tasklet()
Dath9k.h668 OK, /* no change needed */ enumerator
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-class-ubi150 Contains ASCII "0\n" if the UBI volume is OK, and ASCII "1\n"
/linux-4.4.14/Documentation/locking/
Drt-mutex-design.txt475 is OK, since plist_del does nothing if the plist node is not on any
494 process as the tasked being worked on, we are OK.
517 If you don't quite understand the above, that's OK. You don't have to,
558 OK, now let's take a look at the detailed walk through of what happens when
633 OK that we set that flag early, since now it is cleared.
/linux-4.4.14/Documentation/spi/
Dspidev149 same transfer. It's even OK if those are the same buffer.
/linux-4.4.14/drivers/media/pci/ngene/
Dngene.h244 OK = 0, enumerator
/linux-4.4.14/Documentation/arm/
DREADME146 This also seems to work OK, but hasn't been stressed much lately. It
/linux-4.4.14/Documentation/input/
Dxpad.txt54 in game functionality were OK. However, I find it rather difficult to
/linux-4.4.14/Documentation/driver-model/
Dplatform.txt183 be probed later if another device registers. (Which is OK, since
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt2330 OK Linux usermode 2.4.5-9um #1 Wed Jun 20 22:47:08 EDT 2001 i686
2353 OK
2372 OK
2374 OK
2391 OK
2393 OK
2963 Setting hostname uml [ OK ]
3425 Setting hostname uml [ OK ]
/linux-4.4.14/drivers/gpu/drm/
Ddrm_modes.c1023 MODE_STATUS(OK),
/linux-4.4.14/Documentation/gpio/
Dconsumer.txt155 for spinlock-safe GPIOs it is OK to use them before tasking is enabled, as part
Dgpio-legacy.txt141 a task context. However, for spinlock-safe GPIOs it's OK to use them
258 a task context. However, for spinlock-safe GPIOs it's OK to request GPIOs
/linux-4.4.14/Documentation/ioctl/
Dioctl-number.txt37 Some devices use their major number as the identifier; this is OK, as
/linux-4.4.14/Documentation/vm/
Dfrontswap.txt151 3) OK, how about a quick overview of what this frontswap patch does
/linux-4.4.14/Documentation/cdrom/
Dide-cd288 OK, and the problem is at the filesystem level (i.e., the CDROM is
Dcdrom-standard.tex983 part in section~\ref{cdrom-ioctl}, if your code was OK, these are
/linux-4.4.14/Documentation/hwmon/
Dsysfs-interface696 0: OK
/linux-4.4.14/fs/
Dnamei.c1946 goto OK; in link_path_walk()
1955 OK: in link_path_walk()
/linux-4.4.14/Documentation/video4linux/
Dv4l2-controls.txt361 If s_ctrl returns 0 (OK), then the control framework will copy the new final
/linux-4.4.14/arch/blackfin/
DKconfig962 interrupt latency issues, it is safe and OK to turn this off.
/linux-4.4.14/tools/perf/util/intel-pt-decoder/
Dx86-opcode-map.txt357 # bnd registers and Ev for everything else is OK because the instruction
/linux-4.4.14/arch/x86/lib/
Dx86-opcode-map.txt357 # bnd registers and Ev for everything else is OK because the instruction
/linux-4.4.14/Documentation/block/
Dbiodoc.txt331 _last works OK in this case, and is not a problem, as I mentioned earlier