Home
last modified time | relevance | path

Searched refs:wrong (Results 1 – 25 of 177) sorted by relevance

12345678

/Linux-v4.19/Documentation/networking/
Dxfrm_proc.txt25 i.e. Either inbound SPI, address, or IPsec protocol at SA is wrong
28 e.g. SA key is wrong
43 e.g. Inbound SAs are correct but SP rule is wrong
/Linux-v4.19/lib/
Dtest_uuid.c45 static void __init test_uuid_failed(const char *prefix, bool wrong, bool be, in test_uuid_failed() argument
51 wrong ? "passed on wrong" : "failed on", in test_uuid_failed()
Datomic64_test.c88 #define CMPXCHG_FAMILY_TEST(bit, init, new, wrong) \ argument
93 init, init, init, wrong, new); \
/Linux-v4.19/arch/xtensa/
DKconfig.debug8 This check can spot missing TLB invalidation/wrong PTE permissions/
31 It is easy to make wrong hardware configuration, this test should catch it early.
/Linux-v4.19/tools/testing/selftests/x86/
Dtrivial_32bit_program.c8 # error wrong architecture
Dtrivial_64bit_program.c8 # error wrong architecture
/Linux-v4.19/drivers/staging/goldfish/
DREADME4 - Fix the wrong user page DMA (moving to ALSA may fix that too)
/Linux-v4.19/arch/arm/boot/dts/
Ddove-cubox-es.dts10 /* sdio0 card detect is connected to wrong pin on CuBox ES */
/Linux-v4.19/Documentation/process/
Dmanagement-style.rst50 Namely that you are in the wrong job, and that **they** should be managing
61 can be made small by just always making sure that if you were wrong (and
62 you **will** be wrong), you can always undo the damage later by
64 **two** inconsequential decisions - the wrong one **and** the right one.
90 wrong is sometimes very hard indeed.
102 might be the wrong thing. You should always reserve the right to change
129 something wrong with both projects, and the reason the people involved
130 couldn't decide was that they were both wrong. You end up coming up
218 Things will go wrong, and people want somebody to blame. Tag, you're it.
251 somebody else puts on airs, it **really** rubs us the wrong way. You may
/Linux-v4.19/drivers/staging/xgifb/
DTODO9 - remove useless/wrong/unused code...
/Linux-v4.19/arch/mips/loongson64/
DKconfig111 this option at first, otherwise, You will get wrong system time.
123 this option at first, otherwise, You will get wrong system time.
/Linux-v4.19/Documentation/hwmon/
Dadm102543 properly, you'll have a wrong +12V reading or a wrong VID reading. The way
/Linux-v4.19/arch/x86/boot/
Dsetup.ld60 . = ASSERT(hdr == 0x1f1, "The setup header has the wrong offset!");
/Linux-v4.19/Documentation/EDID/
DHOWTO.txt7 booting or it displays the wrong area. Cases when this happens are:
55 most probably complain about a wrong CRC. Fortunately, the utility also
/Linux-v4.19/Documentation/power/
Dtricks.txt13 wrong, force fsck when you have a chance]
/Linux-v4.19/Documentation/ABI/testing/
Ddebugfs-ec20 not get switched on again after you did a wrong write.
/Linux-v4.19/Documentation/devicetree/bindings/hwmon/
Dgpio-fan.txt12 - alarm-gpios: This pin going active indicates something is wrong with
/Linux-v4.19/Documentation/devicetree/bindings/power/supply/
Dltc2941.txt14 negative value when the battery has been connected to the wrong end of the
/Linux-v4.19/scripts/coccinelle/misc/
Dbadty.cocci3 //# This makes an effort to find cases where the argument to sizeof is wrong
/Linux-v4.19/Documentation/media/dvb-drivers/
Dfaq.rst121 which ifconfig outputs. (Note: If the MAC address is wrong,
124 all then maybe the PID is wrong. If there are error packets,
125 then either the PID is wrong or the stream does not conform to
/Linux-v4.19/Documentation/w1/slaves/
Dw1_ds241344 The driver is checking this complement, and when it is wrong then it is
/Linux-v4.19/scripts/coccinelle/tests/
Dodd_ptr_err.cocci3 //# IS_ERR that is wrong.
/Linux-v4.19/tools/scripts/
Dutilities.mak142 # trying too hard and getting things wrong).
152 # trying too hard and getting things wrong).
/Linux-v4.19/Documentation/devicetree/bindings/eeprom/
Dat24.txt60 manual of your device, that value varies a lot. A wrong value
/Linux-v4.19/Documentation/cpu-freq/
Damd-powernow.txt7 Note that the driver's will not load on the "wrong" hardware,

12345678