| /linux-6.12.1/Documentation/networking/ |
| D | xfrm_proc.rst | 33 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.12.1/lib/ |
| D | test_uuid.c | 45 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()
|
| D | atomic64_test.c | 84 #define CMPXCHG_FAMILY_TEST(bit, init, new, wrong) \ argument
89 init, init, init, wrong, new); \
|
| /linux-6.12.1/arch/xtensa/ |
| D | Kconfig.debug | 8 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.12.1/tools/testing/selftests/x86/ |
| D | trivial_32bit_program.c | 8 # error wrong architecture
|
| D | trivial_64bit_program.c | 8 # error wrong architecture
|
| /linux-6.12.1/Documentation/process/ |
| D | management-style.rst | 51 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.12.1/arch/arm/boot/dts/marvell/ |
| D | dove-cubox-es.dts | 10 /* sdio0 card detect is connected to wrong pin on CuBox ES */
|
| /linux-6.12.1/Documentation/hwmon/ |
| D | adm1025.rst | 52 properly, you'll have a wrong +12V reading or a wrong VID reading. The way
|
| /linux-6.12.1/arch/x86/boot/ |
| D | setup.ld | 68 . = ASSERT(hdr == 0x1f1, "The setup header has the wrong offset!");
|
| /linux-6.12.1/Documentation/power/ |
| D | tricks.rst | 15 wrong, force fsck when you have a chance]
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | debugfs-ec | 21 not get switched on again after you did a wrong write.
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | edid.rst | 13 booting or it displays the wrong area. Cases when this happens are:
|
| /linux-6.12.1/scripts/coccinelle/misc/ |
| D | badty.cocci | 4 //# This makes an effort to find cases where the argument to sizeof is wrong
|
| /linux-6.12.1/Documentation/w1/slaves/ |
| D | w1_ds2413.rst | 53 The driver is checking this complement, and when it is wrong then it is
|
| /linux-6.12.1/Documentation/driver-api/mei/ |
| D | mei.rst | 106 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.12.1/scripts/coccinelle/tests/ |
| D | odd_ptr_err.cocci | 4 //# IS_ERR that is wrong.
|
| D | unsigned_lesser_than_zero.cocci | 4 /// usually wrong type of variable.
|
| /linux-6.12.1/arch/mips/loongson2ef/ |
| D | Kconfig | 84 this option at first, otherwise, You will get wrong system time.
|
| /linux-6.12.1/Documentation/admin-guide/media/ |
| D | faq.rst | 187 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
|
| /linux-6.12.1/Documentation/driver-api/firmware/ |
| D | request_firmware.rst | 77 If something went wrong request_firmware() returns non-zero and fw_entry
|
| /linux-6.12.1/Documentation/userspace-api/gpio/ |
| D | error-codes.rst | 64 It's a 'Something is wrong, I give up!' type of error.
|
| /linux-6.12.1/tools/scripts/ |
| D | utilities.mak | 142 # trying too hard and getting things wrong).
152 # trying too hard and getting things wrong).
|
| /linux-6.12.1/Documentation/i2c/ |
| D | fault-codes.rst | 18 result for an operation ... it doesn't indicate that anything is wrong
76 This rather vague error means something went wrong when
|
| /linux-6.12.1/Documentation/admin-guide/cgroup-v1/ |
| D | cpuacct.rst | 46 - It is theoretically possible to see wrong values for user and system times.
|