Home
last modified time | relevance | path

Searched full:correctly (Results 1 – 25 of 3061) sorted by relevance

12345678910>>...123

/kernel/linux/linux-4.19/fs/nls/
DKconfig46 DOS/Windows partitions correctly. This does apply to the filenames
58 DOS/Windows partitions correctly. This does apply to the filenames
70 DOS/Windows partitions correctly. This does apply to the filenames
83 DOS/Windows partitions correctly. This does apply to the filenames
99 DOS/Windows partitions correctly. This does apply to the filenames
114 DOS/Windows partitions correctly. This does apply to the filenames
125 DOS/Windows partitions correctly. This does apply to the filenames
136 DOS/Windows partitions correctly. This does apply to the filenames
147 DOS/Windows partitions correctly. This does apply to the filenames
158 DOS/Windows partitions correctly. This does apply to the filenames
[all …]
/kernel/linux/linux-5.10/fs/nls/
DKconfig47 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 …]
/kernel/linux/linux-4.19/include/linux/mfd/
Ddb8500-prcmu.h297 * @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 …]
/kernel/linux/linux-5.10/include/linux/mfd/
Ddb8500-prcmu.h297 * @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 …]
/kernel/linux/linux-5.10/tools/testing/selftests/vm/
Dhugetlb_reparenting_test.sh197 echo Assert memory charged correctly for parent use.
202 echo Assert memory charged correctly for child use.
207 echo Assert memory reparent correctly.
212 echo Assert memory uncharged correctly.
227 echo Assert memory charged correctly for child only use.
231 echo Assert memory reparent correctly.
236 echo Assert memory uncharged correctly.
/kernel/linux/linux-5.10/tools/testing/selftests/drivers/net/mlxsw/
Drtnetlink.sh204 # interface (RIF) is correctly deleted and not leaked. See commit
228 # Test that when a bridge with VLAN interfaces is deleted, we correctly
270 # If we did not handle references correctly, then this should produce a
313 # correctly
393 # reference counted correctly and destroyed when should. We use the
440 # Test that VLAN devices are correctly deleted / unlinked when enslaved
454 # If we did not handle the situation correctly, then these operations
492 # Test that ports are correctly unlinked from their LAG master, when
529 # Test that LAG device is correctly deleted, when the LAG and its VLAN
546 # Test that uppers of a VLAN interface are correctly sanitized
Dvxlan_flooding.sh6 # 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
/kernel/linux/linux-4.19/drivers/ras/
DKconfig25 correctly, including avoiding data corruption, whereas Availability
27 be functioning correctly. For example, a server may run forever and
/kernel/linux/linux-5.10/drivers/ras/
DKconfig26 correctly, including avoiding data corruption, whereas Availability
28 be functioning correctly. For example, a server may run forever and
/kernel/linux/linux-5.10/tools/testing/selftests/pidfd/
Dpidfd_setns_test.c404 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()
/kernel/linux/linux-4.19/drivers/misc/lkdtm/
Dheap.c13 * correctly.
86 pr_info("Memory correctly poisoned (%x)\n", saw); in lkdtm_READ_AFTER_FREE()
142 pr_info("Memory correctly poisoned (%x)\n", saw); in lkdtm_READ_BUDDY_AFTER_FREE()
/kernel/linux/linux-4.19/drivers/gpu/drm/vmwgfx/device_include/
Dsvga3d_devcaps.h246 * that can be expected to work correctly with a DXContext?
249 * anything in excess of this cap is not guaranteed to render correctly.
255 * correctly.
265 * work correctly with a DX context?
268 * anything in excess of this cap is not guaranteed to render correctly.
/kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/
Ddm-flakey.rst44 Read I/O is handled correctly.
48 Read I/O is handled correctly.
/kernel/linux/linux-5.10/include/linux/
Deventpoll.h39 * correctly files that are closed without being removed from the eventpoll
58 * descriptor. We need to handle this by correctly unlinking it in eventpoll_release()
/kernel/linux/linux-4.19/include/linux/
Deventpoll.h44 * correctly files that are closed without being removed from the eventpoll
63 * descriptor. We need to handle this by correctly unlinking it in eventpoll_release()
/kernel/linux/linux-5.10/drivers/misc/lkdtm/
Dheap.c17 * correctly.
91 pr_info("Memory correctly poisoned (%x)\n", saw); in lkdtm_READ_AFTER_FREE()
147 pr_info("Memory correctly poisoned (%x)\n", saw); in lkdtm_READ_BUDDY_AFTER_FREE()
/kernel/linux/linux-5.10/drivers/gpu/drm/vmwgfx/device_include/
Dsvga3d_devcaps.h242 * that can be expected to work correctly with a DXContext?
245 * anything in excess of this cap is not guaranteed to render correctly.
251 * correctly.
261 * work correctly with a DX context?
264 * anything in excess of this cap is not guaranteed to render correctly.
/kernel/linux/linux-4.19/Documentation/filesystems/nfs/
Dfault_injection.txt8 observe how the client reacts and if it manages to recover its state correctly.
29 correctly.
/kernel/linux/linux-5.10/fs/affs/
DChanges71 - 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.
/kernel/linux/linux-4.19/fs/affs/
DChanges71 - 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.
/kernel/linux/linux-5.10/tools/testing/selftests/splice/
Dshort_splice_read.sh5 # bugs like 11990a5bd7e5 ("module: Correctly truncate sysfs sections output")
62 echo "ok: $title correctly failed" >&2
/kernel/linux/linux-4.19/tools/power/cpupower/debug/kernel/
Dcpufreq-test_tsc.c19 * TSC-based delay routine on the Linux kernel does not correctly
109 MODULE_DESCRIPTION("Verify the TSC cpufreq notifier working correctly -- needs ACPI-enabled system"…
/kernel/linux/linux-5.10/tools/power/cpupower/debug/kernel/
Dcpufreq-test_tsc.c20 * 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"…
/kernel/linux/linux-5.10/security/integrity/platform_certs/
Defi_parser.c32 * 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
/kernel/linux/linux-4.19/Documentation/RCU/
Dtorture.txt200 automatic determination as to whether RCU operated correctly.
226 correctly. This value should be zero.
229 family of functions is not working correctly.
258 The output displayed above was taken from a correctly working

12345678910>>...123