| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | highuid.rst | 22 properly with huge UIDs. If it can deal with 64-bit file offsets on all
33 uses the 32-bit UID system calls properly otherwise.
43 - Validate that all filesystems behave properly.
78 - make sure that the UID mapping feature of AX25 networking works properly
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | highuid.rst | 22 properly with huge UIDs. If it can deal with 64-bit file offsets on all
33 uses the 32-bit UID system calls properly otherwise.
43 - Validate that all filesystems behave properly.
78 - make sure that the UID mapping feature of AX25 networking works properly
|
| /kernel/linux/linux-5.10/drivers/misc/lkdtm/ |
| D | stackleak.c | 3 * This code tests that the current task stack is properly erased (filled
77 pr_err("FAIL: the thread stack is NOT properly erased\n"); in lkdtm_STACKLEAK_ERASING()
80 pr_info("OK: the rest of the thread stack is properly erased\n"); in lkdtm_STACKLEAK_ERASING()
|
| /kernel/linux/linux-6.6/mm/ |
| D | balloon_compaction.c | 35 * Driver must call this function to properly enqueue balloon pages before
65 * Driver must call this function to properly de-allocate a previous enlisted
118 * Driver must call this function to properly allocate a new balloon page.
139 * Drivers must call this function to properly enqueue a new allocated balloon
162 * Driver must call this function to properly dequeue a previously enqueued page
|
| /kernel/linux/linux-5.10/mm/ |
| D | balloon_compaction.c | 35 * Driver must call this function to properly enqueue balloon pages before
65 * Driver must call this function to properly de-allocate a previous enlisted
118 * Driver must call this function to properly allocate a new balloon page.
139 * Drivers must call this function to properly enqueue a new allocated balloon
162 * Driver must call this function to properly dequeue a previously enqueued page
|
| /kernel/linux/linux-6.6/tools/testing/selftests/sync/ |
| D | sync_wait.c | 64 "Fence did not signal properly!\n"); in test_fence_multi_timeline_wait()
70 "Fence did not signal properly!\n"); in test_fence_multi_timeline_wait()
76 "Fence did not signal properly!\n"); in test_fence_multi_timeline_wait()
|
| /kernel/linux/linux-5.10/tools/testing/selftests/sync/ |
| D | sync_wait.c | 64 "Fence did not signal properly!\n"); in test_fence_multi_timeline_wait()
70 "Fence did not signal properly!\n"); in test_fence_multi_timeline_wait()
76 "Fence did not signal properly!\n"); in test_fence_multi_timeline_wait()
|
| /kernel/linux/linux-6.6/drivers/misc/lkdtm/ |
| D | stackleak.c | 3 * This code tests that the current task stack is properly erased (filled
117 pr_err("FAIL: the thread stack is NOT properly erased!\n"); in check_stackleak_irqoff()
119 pr_info("OK: the rest of the thread stack is properly erased\n"); in check_stackleak_irqoff()
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | f71882fg.rst | 145 properly.
162 RPM mode, it will also set fan#_full_speed properly, if it does not then
163 fan control will not work properly, unless you set a sane fan#_full_speed
|
| D | adm1025.rst | 52 properly, you'll have a wrong +12V reading or a wrong VID reading. The way
54 process, assuming that the BIOS set it up properly beforehand. If it turns
|
| /kernel/linux/linux-6.6/Documentation/networking/dsa/ |
| D | bcm_sf2.rst | 71 in order to properly configure them. By default, the SF2 pseudo-PHY address, and
86 firmware gets reloaded. The SF2 driver relies on such events to properly set its
87 MoCA interface carrier state and properly report this to the networking stack.
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | volatile-considered-harmful.rst | 23 unwanted optimization. If they are being used properly, there will be no
25 almost certainly a bug in the code somewhere. In properly-written kernel
106 been properly thought through.
|
| /kernel/linux/linux-6.6/Documentation/hwmon/ |
| D | f71882fg.rst | 145 properly.
162 RPM mode, it will also set fan#_full_speed properly, if it does not then
163 fan control will not work properly, unless you set a sane fan#_full_speed
|
| D | adm1025.rst | 52 properly, you'll have a wrong +12V reading or a wrong VID reading. The way
54 process, assuming that the BIOS set it up properly beforehand. If it turns
|
| /kernel/linux/linux-5.10/Documentation/networking/dsa/ |
| D | bcm_sf2.rst | 71 in order to properly configure them. By default, the SF2 pseudo-PHY address, and
86 firmware gets reloaded. The SF2 driver relies on such events to properly set its
87 MoCA interface carrier state and properly report this to the networking stack.
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | volatile-considered-harmful.rst | 23 unwanted optimization. If they are being used properly, there will be no
25 almost certainly a bug in the code somewhere. In properly-written kernel
106 been properly thought through.
|
| /kernel/linux/linux-5.10/tools/testing/selftests/arm64/signal/testcases/ |
| D | fake_sigreturn_bad_size.c | 47 /* and terminate properly */ in fake_sigreturn_bad_size_run()
63 /* and terminate properly */ in fake_sigreturn_bad_size_run()
|
| /kernel/linux/linux-5.10/arch/c6x/ |
| D | Kconfig | 83 Note that your board must be properly built and your board
84 port must properly enable any big-endian related features
|
| /kernel/linux/linux-6.6/tools/testing/selftests/arm64/signal/testcases/ |
| D | fake_sigreturn_bad_size.c | 47 /* and terminate properly */ in fake_sigreturn_bad_size_run()
63 /* and terminate properly */ in fake_sigreturn_bad_size_run()
|
| /kernel/linux/linux-5.10/Documentation/x86/i386/ |
| D | IO-APIC.rst | 81 between the PIRQ lines. (distributing IRQ sources properly is not a
107 permute all IRQ numbers properly ... it will take some time though. An
109 won't function properly (e.g. if it's inserted as a module).
|
| /kernel/linux/linux-6.6/Documentation/arch/x86/i386/ |
| D | IO-APIC.rst | 81 between the PIRQ lines. (distributing IRQ sources properly is not a
107 permute all IRQ numbers properly ... it will take some time though. An
109 won't function properly (e.g. if it's inserted as a module).
|
| /kernel/linux/linux-6.6/lib/ |
| D | kobject.c | 326 * This function will properly initialize a kobject such that it can then
331 * the memory is cleaned up properly.
342 err_str = "must have a ktype to be initialized properly!\n"; in kobject_init()
370 pr_err("can not set name properly!\n"); in kobject_add_varg()
395 * userspace is properly notified of this kobject's creation.
398 * called to properly clean up the memory associated with the
404 * in order to properly clean up the memory associated with the object.
407 * when the use of the object is finished in order to properly free
444 * properly clean up the memory associated with the object. This is the
865 pr_err("must have a ktype to be initialized properly!\n"); in kset_register()
[all …]
|
| /kernel/linux/linux-5.10/lib/ |
| D | kobject.c | 350 * This function will properly initialize a kobject such that it can then
355 * the memory is cleaned up properly.
366 err_str = "must have a ktype to be initialized properly!\n"; in kobject_init()
394 pr_err("kobject: can not set name properly!\n"); in kobject_add_varg()
419 * userspace is properly notified of this kobject's creation.
422 * called to properly clean up the memory associated with the
428 * in order to properly clean up the memory associated with the object.
431 * when the use of the object is finished in order to properly free
468 * properly clean up the memory associated with the object. This is the
886 pr_err("must have a ktype to be initialized properly!\n"); in kset_register()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/scheduler/ |
| D | sched-debug.rst | 23 detect if pages are properly placed or if the data should be migrated to a
31 behaviour. If pages are properly placed then the scan delay increases,
|
| /kernel/linux/linux-5.10/drivers/scsi/arm/ |
| D | Kconfig | 22 implement this properly, so the safe answer is N.
32 don't implement it properly, so the safe answer is N.
|