/Linux-v5.15/fs/nls/ |
D | Kconfig | 47 DOS/Windows partitions correctly. This does apply to the filenames 59 DOS/Windows partitions correctly. This does apply to the filenames 71 DOS/Windows partitions correctly. This does apply to the filenames 84 DOS/Windows partitions correctly. This does apply to the filenames 100 DOS/Windows partitions correctly. This does apply to the filenames 115 DOS/Windows partitions correctly. This does apply to the filenames 126 DOS/Windows partitions correctly. This does apply to the filenames 137 DOS/Windows partitions correctly. This does apply to the filenames 148 DOS/Windows partitions correctly. This does apply to the filenames 159 DOS/Windows partitions correctly. This does apply to the filenames [all …]
|
/Linux-v5.15/include/linux/mfd/ |
D | db8500-prcmu.h | 297 * @PLLARMLOCKP_ERR: PLLARM has not been correctly locked in given time 298 * @PLLDDRLOCKP_ERR: PLLDDR has not been correctly locked in the given time 299 * @PLLSOC0LOCKP_ERR: PLLSOC0 has not been correctly locked in the given time 300 * @PLLSOC1LOCKP_ERR: PLLSOC1 has not been correctly locked in the given time 301 * @ARMWFI_ERR: The ARM WFI has not been correctly executed in the given time 304 * @ROMCODESAVECONTEXT: The Romcode didn.t correctly save it secure context 306 * through I2C has not been correctly executed in the given time 308 * through I2C has not been correctly executed in the given time 310 * I2C has not been correctly executed in the given time 312 * through I2C has not been correctly executed in the given time [all …]
|
/Linux-v5.15/tools/testing/selftests/vm/ |
D | hugetlb_reparenting_test.sh | 200 echo Assert memory charged correctly for parent use. 205 echo Assert memory charged correctly for child use. 210 echo Assert memory reparent correctly. 215 echo Assert memory uncharged correctly. 230 echo Assert memory charged correctly for child only use. 234 echo Assert memory reparent correctly. 239 echo Assert memory uncharged correctly.
|
/Linux-v5.15/tools/testing/selftests/lkdtm/ |
D | tests.txt | 22 READ_AFTER_FREE call trace:|Memory correctly poisoned 24 READ_BUDDY_AFTER_FREE call trace:|Memory correctly poisoned
|
/Linux-v5.15/tools/testing/selftests/pidfd/ |
D | pidfd_setns_test.c | 404 TH_LOG("setns failed to place us correctly into %s namespace of %d via pidfd %d", in TEST_F() 408 TH_LOG("Managed to correctly setns to %s namespace of %d via pidfd %d", in TEST_F() 440 TH_LOG("setns failed to place us correctly into %s namespace of %d via nsfd %d", in TEST_F() 444 TH_LOG("Managed to correctly setns to %s namespace of %d via nsfd %d", in TEST_F() 485 TH_LOG("setns failed to place us correctly into %s namespace of %d", in TEST_F() 488 TH_LOG("Managed to correctly setns to %s namespace of %d", in TEST_F() 532 TH_LOG("%m - Correctly failed to setns to %s namespace of %d via pidfd %d", in TEST_F() 541 TH_LOG("%m - Correctly failed to setns to %s namespace of %d via nsfd %d", in TEST_F()
|
/Linux-v5.15/drivers/ras/ |
D | Kconfig | 26 correctly, including avoiding data corruption, whereas Availability 28 be functioning correctly. For example, a server may run forever and
|
/Linux-v5.15/tools/testing/selftests/drivers/net/mlxsw/ |
D | vxlan_flooding.sh | 6 # verifies that packets are correctly flooded in various cases such as deletion 233 # and check that packet is flooded correctly when we remove a record 246 # Delete the first record and make sure the packet is flooded correctly 258 # Delete the last record and make sure the packet is flooded correctly 271 # entries are correctly removed
|
D | rtnetlink.sh | 211 # interface (RIF) is correctly deleted and not leaked. See commit 235 # Test that when a bridge with VLAN interfaces is deleted, we correctly 277 # If we did not handle references correctly, then this should produce a 320 # correctly 400 # reference counted correctly and destroyed when should. We use the 489 # Test that VLAN devices are correctly deleted / unlinked when enslaved 503 # If we did not handle the situation correctly, then these operations 541 # Test that ports are correctly unlinked from their LAG master, when 578 # Test that LAG device is correctly deleted, when the LAG and its VLAN 595 # Test that uppers of a VLAN interface are correctly sanitized
|
/Linux-v5.15/tools/perf/pmu-events/arch/x86/amdzen3/ |
D | core.json | 59 …"PublicDescription": "The number of near returns retired that were not correctly predicted by the … 65 …"PublicDescription": "The number of indirect branches retired that were not correctly predicted. E… 112 …": "The number of retired conditional branch instructions that were not correctly predicted becaus…
|
/Linux-v5.15/Documentation/admin-guide/device-mapper/ |
D | dm-flakey.rst | 44 Read I/O is handled correctly. 48 Read I/O is handled correctly.
|
/Linux-v5.15/include/linux/ |
D | eventpoll.h | 31 * correctly files that are closed without being removed from the eventpoll 50 * descriptor. We need to handle this by correctly unlinking it in eventpoll_release()
|
D | ptr_ring.h | 262 * to work correctly. in __ptr_ring_discard_one() 479 * in __ptr_ring_discard_one work correctly. in __ptr_ring_set_size() 507 * resize you must make sure all uses nest correctly. 586 * resize you must make sure all uses nest correctly. 615 * resize you must make sure all uses nest correctly.
|
/Linux-v5.15/fs/affs/ |
D | Changes | 71 - correctly cut off long file names for compares 72 - correctly initialize s_last_bmap 199 correctly byte-swapped. Since most of the users of the 214 invalid filenames didn't work correctly.
|
/Linux-v5.15/include/uapi/linux/ |
D | seg6_local.h | 90 * packets that have been CORRECTLY processed by an SRv6 Behavior instance 94 * of traffic in bytes of all packets that have been CORRECTLY processed by
|
/Linux-v5.15/tools/testing/selftests/splice/ |
D | short_splice_read.sh | 5 # bugs like 11990a5bd7e5 ("module: Correctly truncate sysfs sections output") 62 echo "ok: $title correctly failed" >&2
|
/Linux-v5.15/security/integrity/platform_certs/ |
D | efi_parser.c | 32 * Error EBADMSG is returned if the list doesn't parse correctly and 0 is 33 * returned if the list was parsed correctly. No error can be returned from
|
/Linux-v5.15/drivers/misc/lkdtm/ |
D | powerpc.c | 39 * This triggers exception, If handled correctly we must recover in inject_vmalloc_slb_multihit() 58 * This triggers exception, If handled correctly we must recover in inject_kmalloc_slb_multihit()
|
D | heap.c | 43 * correctly. 118 pr_info("Memory correctly poisoned (%x)\n", saw); in lkdtm_READ_AFTER_FREE() 175 pr_info("Memory correctly poisoned (%x)\n", saw); in lkdtm_READ_BUDDY_AFTER_FREE()
|
/Linux-v5.15/tools/power/cpupower/debug/kernel/ |
D | cpufreq-test_tsc.c | 20 * TSC-based delay routine on the Linux kernel does not correctly 110 MODULE_DESCRIPTION("Verify the TSC cpufreq notifier working correctly -- needs ACPI-enabled system"…
|
/Linux-v5.15/tools/perf/pmu-events/arch/x86/amdzen1/ |
D | core.json | 23 … "The number of branch instructions retired, of any type, that were not correctly predicted. This … 59 …"PublicDescription": "The number of near returns retired that were not correctly predicted by the …
|
/Linux-v5.15/arch/arm/mach-davinci/ |
D | Kconfig | 153 the switch correctly. 216 sets the multiplexing correctly, say N. Otherwise, or if unsure,
|
/Linux-v5.15/arch/mips/math-emu/ |
D | dp_sqrt.c | 110 /* twiddle last bit to force y correctly rounded */ in ieee754dp_sqrt() 141 /* adjust scalx for correctly rounded sqrt(x) */ in ieee754dp_sqrt()
|
/Linux-v5.15/tools/perf/pmu-events/arch/x86/amdzen2/ |
D | core.json | 23 … "The number of branch instructions retired, of any type, that were not correctly predicted. This … 59 …"PublicDescription": "The number of near returns retired that were not correctly predicted by the …
|
/Linux-v5.15/Documentation/PCI/ |
D | acpi-info.rst | 28 can work correctly even on a system with new devices unknown to the OS. 35 is defined, an old OS needs to operate correctly even though it ignores the 57 BIOSes didn't use that bit correctly. The result is that the current ACPI
|
/Linux-v5.15/Documentation/i2c/ |
D | fault-codes.rst | 22 to respond correctly. Other code may need to rely on YOUR code reporting 23 the right fault code, so that it can (in turn) behave correctly.
|