| /linux/fs/ubifs/ |
| H A 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/net/appletalk/ |
| H A D | Kconfig | 23 <http://www.tldp.org/docs.html#howto>, contains valuable
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-trigger-sysfs | 8 into an in kernel buffer. This approach can be valuable during
|
| H A D | sysfs-firmware-dmi-entries | 7 information is often valuable to userland, especially in
|
| /linux/Documentation/maintainer/ |
| H A D | modifying-patches.rst | 48 Whatever the format, this information provides a valuable help to people
|
| /linux/Documentation/hwmon/ |
| H A D | pcf8591.rst | 18 - valuable contributions by Jan M. Sendler <sendler@sendler.de>,
|
| /linux/Documentation/scsi/ |
| H A D | dc395x.rst | 112 reliable driver, there is a chance, that it will kill your valuable data.
|
| /linux/Documentation/process/ |
| H A D | 8.Conclusion.rst | 23 Beyond that, a valuable resource for kernel developers is:
|
| H A D | researcher-guidelines.rst | 61 such requests deprives the community of valuable contributor time and is
|
| H A D | maintainer-kvm-x86.rst | 329 context of why a change was made is highly valuable for future readers.
|
| H A D | coding-style.rst | 488 because it is a simple way to add valuable information for the reader.
|
| /linux/drivers/mtd/ |
| H A 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/tools/memory-model/scripts/ |
| H A D | README | 102 this check is nevertheless valuable because it can find errors in the
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A 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/Documentation/userspace-api/media/v4l/ |
| H A D | userp.rst | 70 possibly completing the requested DMA and overwriting valuable data.
|
| /linux/Documentation/virt/kvm/x86/ |
| H A D | nested-vmx.rst | 239 And valuable reviews by:
|
| /linux/tools/testing/selftests/tc-testing/ |
| H A D | README | 205 Jamal Hadi Salim, for providing valuable test cases
|
| /linux/Documentation/admin-guide/media/ |
| H A D | faq.rst | 163 valuable information:
|
| /linux/Documentation/gpu/ |
| H A D | introduction.rst | 149 valuable to go through older material to understand the rationale and context
|
| H A D | drm-vm-bind-async.rst | 112 questionable and should be rejected until there is a valuable use-case.
|
| /linux/Documentation/core-api/ |
| H A D | genericirq.rst | 70 also valuable for (sub)architectures which need specific quirks in the
|
| /linux/Documentation/sound/designs/ |
| H A D | compress-offload.rst | 326 - Rakesh Ughreja for valuable feedback
|
| /linux/Documentation/arch/x86/ |
| H A D | sgx.rst | 249 SGX workloads, (or just any new workloads), and migrate all valuable
|
| /linux/Documentation/driver-api/usb/ |
| H A D | dwc3.rst | 186 Synopsys Databook will be **really** valuable in this case.
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | cpusets.rst | 90 This can be especially valuable on:
|