Searched refs:valuable (Results 1 – 25 of 35) sorted by relevance
12
| /Linux-v6.1/fs/ubifs/ |
| D | find.c | 42 static int valuable(struct ubifs_info *c, const struct ubifs_lprops *lprops) in valuable() function
93 if (!in_tree && valuable(c, lprops)) in scan_for_dirty_cb()
360 if (!in_tree && valuable(c, lprops)) in scan_for_free_cb()
600 if (!in_tree && valuable(c, lprops)) in scan_for_idx_cb()
793 if (!in_tree && valuable(c, lprops)) in scan_dirty_idx_cb()
|
| /Linux-v6.1/drivers/acpi/apei/ |
| D | Kconfig | 33 by firmware to produce more valuable hardware error
|
| /Linux-v6.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-v6.1/Documentation/maintainer/ |
| D | modifying-patches.rst | 48 Whatever the format, this information provides a valuable help to people
|
| /Linux-v6.1/Documentation/scsi/ |
| D | dc395x.rst | 115 reliable driver, there is a chance, that it will kill your valuable data.
|
| /Linux-v6.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-v6.1/Documentation/process/ |
| D | 8.Conclusion.rst | 23 Beyond that, a valuable resource for kernel developers is:
|
| D | maintainer-tip.rst | 214 issues, it is valuable to depict the scenario with a table which shows
278 are helpful to identify the original commit and are much more valuable
|
| /Linux-v6.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-v6.1/drivers/net/appletalk/ |
| D | Kconfig | 23 <http://www.tldp.org/docs.html#howto>, contains valuable
|
| /Linux-v6.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-v6.1/Documentation/RCU/ |
| D | arrayRCU.rst | 22 arrays prove to be particularly valuable (which they have not thus far),
|
| /Linux-v6.1/Documentation/userspace-api/media/v4l/ |
| D | userp.rst | 70 possibly completing the requested DMA and overwriting valuable data.
|
| /Linux-v6.1/Documentation/virt/kvm/x86/ |
| D | nested-vmx.rst | 239 And valuable reviews by:
|
| /Linux-v6.1/Documentation/usb/ |
| D | CREDITS | 118 evaluation boards, specs and valuable advices during
|
| /Linux-v6.1/Documentation/admin-guide/media/ |
| D | faq.rst | 163 valuable information:
|
| /Linux-v6.1/Documentation/gpu/ |
| D | introduction.rst | 149 valuable to go through older material to understand the rationale and context
|
| /Linux-v6.1/tools/testing/selftests/tc-testing/ |
| D | README | 252 Jamal Hadi Salim, for providing valuable test cases
|
| /Linux-v6.1/Documentation/core-api/ |
| D | genericirq.rst | 70 also valuable for (sub)architectures which need specific quirks in the
|
| /Linux-v6.1/Documentation/sound/designs/ |
| D | compress-offload.rst | 325 - Rakesh Ughreja for valuable feedback
|
| /Linux-v6.1/Documentation/x86/ |
| D | sgx.rst | 249 SGX workloads, (or just any new workloads), and migrate all valuable
|
| /Linux-v6.1/Documentation/input/ |
| D | input-programming.rst | 131 all the time, or if the device uses a valuable resource (e.g. interrupt), it
|
| /Linux-v6.1/Documentation/driver-api/usb/ |
| D | dwc3.rst | 186 Synopsys Databook will be **really** valuable in this case.
|
12
