Home
last modified time | relevance | path

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

123456789

/linux-6.3-rc2/Documentation/networking/
A Dxfrm_proc.rst33 i.e. Either inbound SPI, address, or IPsec protocol at SA is wrong
37 e.g. SA key is wrong
58 e.g. Inbound SAs are correct but SP rule is wrong
/linux-6.3-rc2/lib/
A 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()
A Datomic64_test.c84 #define CMPXCHG_FAMILY_TEST(bit, init, new, wrong) \ argument
89 init, init, init, wrong, new); \
/linux-6.3-rc2/arch/xtensa/
A 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-6.3-rc2/tools/testing/selftests/x86/
A Dtrivial_32bit_program.c8 # error wrong architecture
A Dtrivial_64bit_program.c8 # error wrong architecture
/linux-6.3-rc2/Documentation/process/
A Dmanagement-style.rst51 Namely that you are in the wrong job, and that **they** should be managing
62 can be made small by just always making sure that if you were wrong (and
63 you **will** be wrong), you can always undo the damage later by
65 **two** inconsequential decisions - the wrong one **and** the right one.
91 wrong is sometimes very hard indeed.
103 might be the wrong thing. You should always reserve the right to change
130 something wrong with both projects, and the reason the people involved
131 couldn't decide was that they were both wrong. You end up coming up
219 Things will go wrong, and people want somebody to blame. Tag, you're it.
252 somebody else puts on airs, it **really** rubs us the wrong way. You may
/linux-6.3-rc2/arch/arm/boot/dts/
A Ddove-cubox-es.dts10 /* sdio0 card detect is connected to wrong pin on CuBox ES */
/linux-6.3-rc2/Documentation/hwmon/
A Dadm1025.rst52 properly, you'll have a wrong +12V reading or a wrong VID reading. The way
/linux-6.3-rc2/arch/x86/boot/
A Dsetup.ld62 . = ASSERT(hdr == 0x1f1, "The setup header has the wrong offset!");
/linux-6.3-rc2/Documentation/power/
A Dtricks.rst15 wrong, force fsck when you have a chance]
/linux-6.3-rc2/Documentation/ABI/testing/
A Ddebugfs-ec21 not get switched on again after you did a wrong write.
/linux-6.3-rc2/Documentation/devicetree/bindings/hwmon/
A Dgpio-fan.txt12 - alarm-gpios: This pin going active indicates something is wrong with
/linux-6.3-rc2/scripts/coccinelle/misc/
A Dbadty.cocci4 //# This makes an effort to find cases where the argument to sizeof is wrong
/linux-6.3-rc2/Documentation/mm/
A Dpage_table_check.rst22 by crashing kernel at the time wrong mapping occurs instead of later which is
/linux-6.3-rc2/Documentation/devicetree/bindings/power/supply/
A Dlltc,ltc294x.yaml37 Can be negative value when the battery has been connected to the wrong end of the resistor.
/linux-6.3-rc2/Documentation/w1/slaves/
A Dw1_ds2413.rst53 The driver is checking this complement, and when it is wrong then it is
/linux-6.3-rc2/scripts/coccinelle/tests/
A Dodd_ptr_err.cocci4 //# IS_ERR that is wrong.
A Dunsigned_lesser_than_zero.cocci4 /// usually wrong type of variable.
/linux-6.3-rc2/arch/mips/loongson2ef/
A DKconfig81 this option at first, otherwise, You will get wrong system time.
/linux-6.3-rc2/tools/scripts/
A Dutilities.mak142 # trying too hard and getting things wrong).
152 # trying too hard and getting things wrong).
/linux-6.3-rc2/Documentation/driver-api/mei/
A Dmei.rst106 ENOTTY No such client (i.e. wrong GUID) or connection is not allowed.
143 ENOTTY No such client (i.e. wrong GUID) or connection is not allowed.
/linux-6.3-rc2/Documentation/driver-api/firmware/
A Drequest_firmware.rst77 If something went wrong request_firmware() returns non-zero and fw_entry
/linux-6.3-rc2/Documentation/i2c/
A Dfault-codes.rst18 result for an operation ... it doesn't indicate that anything is wrong
72 This rather vague error means something went wrong when
/linux-6.3-rc2/Documentation/admin-guide/media/
A Dfaq.rst187 address is wrong, ``dvb_net`` won't get any input; thus you have to
189 packets at all then maybe the PID is wrong. If there are error packets,
190 then either the PID is wrong or the stream does not conform to

Completed in 28 milliseconds

123456789