Searched refs:valuable (Results 1 – 25 of 31) sorted by relevance
12
| /Linux-v5.4/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-v5.4/drivers/acpi/apei/ |
| D | Kconfig | 33 by firmware to produce more valuable hardware error
|
| /Linux-v5.4/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-v5.4/Documentation/scsi/ |
| D | dc395x.txt | 100 reliable driver, there is a chance, that it will kill your valuable data.
|
| /Linux-v5.4/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-v5.4/drivers/mtd/ |
| D | Kconfig | 160 isn't recommended to use with valuable data (anyway if you have
161 valuable data, do backups regardless of software/hardware you
|
| /Linux-v5.4/Documentation/process/ |
| D | 8.Conclusion.rst | 25 Beyond that, a valuable resource for kernel developers is:
|
| /Linux-v5.4/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-v5.4/drivers/net/appletalk/ |
| D | Kconfig | 23 <http://www.tldp.org/docs.html#howto>, contains valuable
|
| /Linux-v5.4/Documentation/RCU/ |
| D | arrayRCU.txt | 20 arrays prove to be particularly valuable (which they have not thus far),
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | userp.rst | 76 possibly completing the requested DMA and overwriting valuable data.
|
| /Linux-v5.4/Documentation/virt/kvm/ |
| D | nested-vmx.txt | 235 And valuable reviews by:
|
| /Linux-v5.4/Documentation/usb/ |
| D | CREDITS | 118 evaluation boards, specs and valuable advices during
|
| /Linux-v5.4/tools/testing/selftests/tc-testing/ |
| D | README | 252 Jamal Hadi Salim, for providing valuable test cases
|
| /Linux-v5.4/Documentation/input/ |
| D | input-programming.rst | 131 all the time, or if the device uses a valuable resource (eg. interrupt), it
|
| /Linux-v5.4/Documentation/core-api/ |
| D | genericirq.rst | 70 also valuable for (sub)architectures which need specific quirks in the
|
| /Linux-v5.4/Documentation/sound/designs/ |
| D | compress-offload.rst | 242 - Rakesh Ughreja for valuable feedback
|
| /Linux-v5.4/Documentation/vm/ |
| D | frontswap.rst | 277 page may be taking up valuable real estate. The frontswap_shrink
|
| /Linux-v5.4/Documentation/driver-api/usb/ |
| D | dwc3.rst | 186 Synopsys Databook will be **really** valuable in this case.
|
| /Linux-v5.4/Documentation/bpf/ |
| D | btf.rst | 701 raw bytes. This is especially valuable for large structure or if your data
|
| /Linux-v5.4/Documentation/scheduler/ |
| D | sched-deadline.rst | 725 is a valuable tool, as it can be used to synthetically recreate certain
|
| /Linux-v5.4/Documentation/admin-guide/cgroup-v1/ |
| D | cpusets.rst | 88 This can be especially valuable on:
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | ras.rst | 828 necessary handling of errors and might loose valuable information for
|
12
