| /Linux-v5.10/arch/powerpc/kernel/ |
| D | prom_init_check.sh | 61 OK=0
65 OK=1
73 OK=1
76 OK=1
80 if [ $OK -eq 0 ]; then
|
| /Linux-v5.10/drivers/net/plip/ |
| D | plip.c | 341 #define OK 0 macro
370 if ((r = (*f)(nl->dev, nl, snd, rcv)) != OK && in plip_bh()
371 (r = plip_bh_timeout_error(nl->dev, nl, snd, rcv, r)) != OK) { in plip_bh()
431 return OK; in plip_bh_timeout_error()
472 return OK; in plip_none()
522 return OK; in plip_receive()
610 return OK; in plip_receive_packet()
688 return OK; in plip_receive_packet()
694 return OK; in plip_receive_packet()
697 return OK; in plip_receive_packet()
[all …]
|
| /Linux-v5.10/tools/testing/selftests/net/ |
| D | ipv6_flowlabel.sh | 21 echo OK. All tests passed
|
| D | so_txtime.sh | 36 echo OK. All tests passed
|
| /Linux-v5.10/tools/testing/kunit/test_data/ |
| D | test_is_test_passed-no_tests_run.log | 5 Checking if /dev/shm is on tmpfs...OK
6 Checking PROT_EXEC mmap in /dev/shm...OK
30 Checking host MADV_REMOVE support...OK
|
| /Linux-v5.10/Documentation/power/ |
| D | video.rst | 112 Asus L2400D s3_mode (3) [#f2]_ (S1 also works OK)
114 Asus L3800C (Radeon M7) s3_bios (2) (S1 also works OK)
119 Compaq Armada E500 - P3-700 none (1) (S1 also works OK)
143 HP Omnibook 5150 none (1), (S1 also works OK)
190 Toshiba Satellite 4030CDT s3_mode (3) (S1 also works OK)
191 Toshiba Satellite 4080XCDT s3_mode (3) (S1 also works OK)
|
| /Linux-v5.10/drivers/net/fddi/skfp/h/ |
| D | sba_def.h | 63 #define OK 0x01 /* ??????? */ macro
|
| /Linux-v5.10/tools/build/tests/ |
| D | run.sh | 70 echo OK
|
| /Linux-v5.10/tools/testing/selftests/bpf/ |
| D | test_tc_tunnel.sh | 282 echo OK
295 echo OK
|
| /Linux-v5.10/tools/testing/selftests/lkdtm/ |
| D | tests.txt | 69 STACKLEAK_ERASING OK: the rest of the thread stack is properly erased
|
| /Linux-v5.10/Documentation/usb/ |
| D | usbip_protocol.rst | 123 | 4 | 4 | 0x00000000 | Status: 0 for OK |
215 | | | | - 0 for OK |
219 | | | | device, if the previous status field was OK (0), |
|
| D | acm.rst | 130 If all this seems to be OK, fire up minicom and set it to talk to the ttyACM
131 device and try typing 'at'. If it responds with 'OK', then everything is
|
| D | gadget_printer.rst | 118 Printer OK
141 To set error status to printer OK::
439 printf(" Printer OK\n");
|
| /Linux-v5.10/arch/arm/boot/dts/ |
| D | logicpd-torpedo-37xx-devkit.dts | 29 * gpio157 is not connected. So this should be OK to keep common for now,
|
| D | ste-nomadik-nhk15.dts | 137 0x02030160 // OK
|
| /Linux-v5.10/drivers/net/ethernet/sis/ |
| D | sis900.h | 200 OK = 0x08000000, DSIZE = 0x00000FFF enumerator
|
| /Linux-v5.10/Documentation/scsi/ |
| D | arcmsr_spec.rst | 20 zDRIVER DATA WRITE OK)
23 (DRIVER DATA READ OK)
28 (IOP331 DATA WRITE OK)
31 (IOP331 DATA READ OK)
|
| /Linux-v5.10/Documentation/userspace-api/media/cec/ |
| D | cec-ioc-receive.rst | 241 * .. _`CEC-TX-STATUS-OK`:
262 of a transmit is just OK or FAIL. In that case this status will be
285 mutually exclusive with :ref:`CEC_TX_STATUS_OK <CEC-TX-STATUS-OK>`.
310 * .. _`CEC-RX-STATUS-OK`:
|
| /Linux-v5.10/Documentation/driver-api/80211/ |
| D | mac80211-advanced.rst | 97 Note: WDS with identical MAC address should almost always be OK
|
| /Linux-v5.10/Documentation/driver-api/serial/ |
| D | n_gsm.rst | 44 and check that it's successful (should return OK) */
|
| /Linux-v5.10/lib/raid6/ |
| D | int.uc | 77 vv = (vv << 1) - (vv >> 7); /* Overflow on the top bit is OK */
|
| /Linux-v5.10/Documentation/ABI/stable/ |
| D | sysfs-driver-mlxreg-io | 6 0 - health failed, 2 - health OK, 3 - ASIC in booting state.
197 0 - OK; 1 - CRC failure; 2 = I2C failure; 3 - in progress.
|
| /Linux-v5.10/tools/testing/selftests/bpf/prog_tests/ |
| D | sockopt.c | 9 OK = 0, enumerator
958 ret = test->error != OK; in run_test()
|
| /Linux-v5.10/tools/perf/tests/ |
| D | make | 352 @echo OK
356 @echo OK
|
| /Linux-v5.10/Documentation/networking/ |
| D | netdev-FAQ.rst | 189 mainline, the better the odds that it is an OK candidate for stable. So
245 OK with that, then perhaps consider mailing security@kernel.org or
283 Q: Any other tips to help ensure my net/net-next patch gets OK'd?
|
