Searched refs:valuable (Results 1 – 25 of 42) sorted by relevance
12
/linux-6.12.1/fs/ubifs/ |
D | find.c | 42 static int valuable(struct ubifs_info *c, const struct ubifs_lprops *lprops) in valuable() function 94 if (!in_tree && valuable(c, lprops)) in scan_for_dirty_cb() 361 if (!in_tree && valuable(c, lprops)) in scan_for_free_cb() 602 if (!in_tree && valuable(c, lprops)) in scan_for_idx_cb() 794 if (!in_tree && valuable(c, lprops)) in scan_dirty_idx_cb()
|
/linux-6.12.1/net/appletalk/ |
D | Kconfig | 23 <http://www.tldp.org/docs.html#howto>, contains valuable
|
/linux-6.12.1/Documentation/ABI/testing/ |
D | sysfs-bus-iio-trigger-sysfs | 8 into an in kernel buffer. This approach can be valuable during
|
D | sysfs-firmware-dmi-entries | 7 information is often valuable to userland, especially in
|
/linux-6.12.1/Documentation/maintainer/ |
D | modifying-patches.rst | 48 Whatever the format, this information provides a valuable help to people
|
/linux-6.12.1/drivers/acpi/apei/ |
D | Kconfig | 33 by firmware to produce more valuable hardware error
|
/linux-6.12.1/Documentation/hwmon/ |
D | pcf8591.rst | 18 - valuable contributions by Jan M. Sendler <sendler@sendler.de>,
|
D | ds1621.rst | 48 - valuable contributions by Jan M. Sendler <sendler@sendler.de>
|
/linux-6.12.1/Documentation/scsi/ |
D | dc395x.rst | 112 reliable driver, there is a chance, that it will kill your valuable data.
|
/linux-6.12.1/drivers/mtd/ |
D | Kconfig | 163 isn't recommended to use with valuable data (anyway if you have 164 valuable data, do backups regardless of software/hardware you
|
/linux-6.12.1/Documentation/process/ |
D | 8.Conclusion.rst | 23 Beyond that, a valuable resource for kernel developers is:
|
D | researcher-guidelines.rst | 61 such requests deprives the community of valuable contributor time and is
|
/linux-6.12.1/tools/memory-model/scripts/ |
D | README | 102 this check is nevertheless valuable because it can find errors in the
|
/linux-6.12.1/Documentation/admin-guide/hw-vuln/ |
D | l1tf.rst | 229 of valuable information from the host OS context depends on the context 231 threads. The amount of valuable data from these contexts cannot be 512 still expose valuable data to a potential attacker. See 523 which might expose valuable information. See
|
/linux-6.12.1/Documentation/userspace-api/media/v4l/ |
D | userp.rst | 70 possibly completing the requested DMA and overwriting valuable data.
|
/linux-6.12.1/Documentation/virt/kvm/x86/ |
D | nested-vmx.rst | 239 And valuable reviews by:
|
/linux-6.12.1/Documentation/usb/ |
D | CREDITS | 118 evaluation boards, specs and valuable advices during
|
/linux-6.12.1/Documentation/kernel-hacking/ |
D | false-sharing.rst | 86 checked, and it is valuable to run specific tools for performance
|
/linux-6.12.1/tools/testing/selftests/tc-testing/ |
D | README | 205 Jamal Hadi Salim, for providing valuable test cases
|
/linux-6.12.1/Documentation/admin-guide/media/ |
D | faq.rst | 163 valuable information:
|
/linux-6.12.1/Documentation/gpu/ |
D | introduction.rst | 149 valuable to go through older material to understand the rationale and context
|
D | drm-vm-bind-async.rst | 112 questionable and should be rejected until there is a valuable use-case.
|
/linux-6.12.1/Documentation/filesystems/bcachefs/ |
D | CodingStyle.rst | 137 else. The experience gained and lessons learned will be valuable for all the
|
/linux-6.12.1/Documentation/core-api/ |
D | genericirq.rst | 70 also valuable for (sub)architectures which need specific quirks in the
|
/linux-6.12.1/Documentation/sound/designs/ |
D | compress-offload.rst | 326 - Rakesh Ughreja for valuable feedback
|
12