Searched full:properly (Results 1 – 25 of 1809) sorted by relevance
12345678910>>...73
| /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
|
| /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()
|
| /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
|
| /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()
|
| /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
|
| /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.
|
| /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.
|
| /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()
|
| /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
|
| /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).
|
| /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.
|
| /linux-5.10/lib/ |
| D | kobject.c | 342 * This function will properly initialize a kobject such that it can then
347 * the memory is cleaned up properly.
358 err_str = "must have a ktype to be initialized properly!\n"; in kobject_init()
386 pr_err("kobject: can not set name properly!\n"); in kobject_add_varg()
411 * userspace is properly notified of this kobject's creation.
414 * called to properly clean up the memory associated with the
420 * in order to properly clean up the memory associated with the object.
423 * when the use of the object is finished in order to properly free
460 * properly clean up the memory associated with the object. This is the
982 * no kset itself. That way we can properly free it when it is in kset_create()
|
| /linux-5.10/arch/m68k/ifpsp060/ |
| D | README | 58 was connected properly; hex image
62 connected properly; hex image
|
| /linux-5.10/Documentation/core-api/ |
| D | kobject.rst | 123 The ktype is required for a kobject to be created properly, as every kobject
131 properly. If the kobject is to be associated with a specific kset,
151 To properly access the name of the kobject, use the function
177 have been initialized properly, as userspace will instantly start to look
415 any other sysfs housekeeping will be handled for the caller properly.
434 For a more complete example of using ksets and kobjects properly, see the
|
| /linux-5.10/tools/power/cpupower/debug/kernel/ |
| D | cpufreq-test_tsc.c | 4 * to work properly after cpufreq transitions. Needs ACPI to work
5 * properly.
|
| /linux-5.10/Documentation/livepatch/ |
| D | cumulative-patches.rst | 81 that are necessary to properly replace any older patch.
102 callback. It is called only when the livepatch is properly disabled.
|
| /linux-5.10/include/uapi/mtd/ |
| D | ubi-user.h | 32 * control device. The caller has to properly fill and pass
47 * device. A &struct ubi_mkvol_req object has to be properly filled and a
61 * device should be used. A &struct ubi_rsvol_req object has to be properly
69 * has to be properly filled and a pointer to it has to be passed to the ioctl.
328 * shortened in order to make it properly aligned. The alignment has to be
336 * BLOBs, without caring about how to properly align them.
|
| /linux-5.10/Documentation/scsi/ |
| D | qlogicfas.rst | 59 Make sure it works properly under DOS. You should also do an initial FDISK
72 that the file copied properly. (Turn off all caching when doing these
|
| /linux-5.10/tools/testing/selftests/mqueue/ |
| D | mq_open_tests.c | 358 * properly follows the default settings in main()
380 printf("Kernel properly honors default setting " in main()
397 printf("Kernel properly limits default values " in main()
400 printf("Kernel does not properly set default " in main()
416 printf("Kernel properly fails to create queue when " in main()
|
| /linux-5.10/kernel/ |
| D | smpboot.c | 341 * If CPU has died properly, set its state to CPU_UP_PREPARE and
346 * properly, but it is up to the arch-specific code to decide.
363 /* The CPU died properly, so just start it up again. */ in cpu_check_up_prepare()
374 * will be reset properly by cpu_set_state_online(). in cpu_check_up_prepare()
|
| /linux-5.10/drivers/staging/media/meson/vdec/ |
| D | TODO | 4 It is at the moment not guaranteed to work properly with a userspace
|
| /linux-5.10/Documentation/powerpc/ |
| D | booting.rst | 13 doesn't follow them properly. In addition, since the advent of the arch/powerpc
76 used by the assembly code to properly disable the MMU
|
| /linux-5.10/Documentation/i2c/busses/ |
| D | i2c-piix4.rst | 42 The PIIX4 (properly known as the 82371AB) is an Intel chip with a lot of
100 not working properly.
|
| /linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class | 13 work properly.
|
12345678910>>...73