| /Linux-v5.4/Documentation/networking/ |
| D | xfrm_proc.txt | 25 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-v5.4/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-v5.4/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-v5.4/tools/testing/selftests/x86/ |
| D | trivial_32bit_program.c | 8 # error wrong architecture
|
| D | trivial_64bit_program.c | 8 # error wrong architecture
|
| /Linux-v5.4/drivers/staging/goldfish/ |
| D | README | 4 - Fix the wrong user page DMA (moving to ALSA may fix that too)
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | dove-cubox-es.dts | 10 /* sdio0 card detect is connected to wrong pin on CuBox ES */
|
| /Linux-v5.4/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-v5.4/Documentation/hwmon/ |
| D | adm1025.rst | 52 properly, you'll have a wrong +12V reading or a wrong VID reading. The way
|
| /Linux-v5.4/arch/mips/loongson64/ |
| D | Kconfig | 110 this option at first, otherwise, You will get wrong system time.
122 this option at first, otherwise, You will get wrong system time.
|
| /Linux-v5.4/arch/x86/boot/ |
| D | setup.ld | 60 . = ASSERT(hdr == 0x1f1, "The setup header has the wrong offset!");
|
| /Linux-v5.4/Documentation/power/ |
| D | tricks.rst | 15 wrong, force fsck when you have a chance]
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | debugfs-ec | 20 not get switched on again after you did a wrong write.
|
| /Linux-v5.4/Documentation/devicetree/bindings/hwmon/ |
| D | gpio-fan.txt | 12 - alarm-gpios: This pin going active indicates something is wrong with
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/supply/ |
| D | ltc2941.txt | 14 negative value when the battery has been connected to the wrong end of the
|
| /Linux-v5.4/scripts/coccinelle/misc/ |
| D | badty.cocci | 4 //# This makes an effort to find cases where the argument to sizeof is wrong
|
| /Linux-v5.4/Documentation/media/dvb-drivers/ |
| D | faq.rst | 123 which ifconfig outputs. (Note: If the MAC address is wrong,
126 all then maybe the PID is wrong. If there are error packets,
127 then either the PID is wrong or the stream does not conform to
|
| /Linux-v5.4/Documentation/w1/slaves/ |
| D | w1_ds2413.rst | 53 The driver is checking this complement, and when it is wrong then it is
|
| /Linux-v5.4/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-v5.4/tools/scripts/ |
| D | utilities.mak | 142 # trying too hard and getting things wrong).
152 # trying too hard and getting things wrong).
|
| /Linux-v5.4/Documentation/cpu-freq/ |
| D | amd-powernow.txt | 7 Note that the driver's will not load on the "wrong" hardware,
|
| /Linux-v5.4/Documentation/driver-api/firmware/ |
| D | request_firmware.rst | 72 If something went wrong request_firmware() returns non-zero and fw_entry
|
| /Linux-v5.4/Documentation/devicetree/bindings/eeprom/ |
| D | at24.txt | 62 manual of your device, that value varies a lot. A wrong value
|
