Searched refs:valuable (Results 1 – 24 of 24) sorted by relevance
| /linux-4.4.14/fs/ubifs/ |
| D | find.c | 54 static int valuable(struct ubifs_info *c, const struct ubifs_lprops *lprops) in valuable() function
105 if (!in_tree && valuable(c, lprops)) in scan_for_dirty_cb()
372 if (!in_tree && valuable(c, lprops)) in scan_for_free_cb()
612 if (!in_tree && valuable(c, lprops)) in scan_for_idx_cb()
815 if (!in_tree && valuable(c, lprops)) in scan_dirty_idx_cb()
|
| /linux-4.4.14/drivers/acpi/apei/ |
| D | Kconfig | 32 by firmware to produce more valuable hardware error
|
| /linux-4.4.14/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-4.4.14/Documentation/hwmon/ |
| D | pcf8591 | 13 valuable contributions by Jan M. Sendler <sendler@sendler.de>,
|
| D | ds1621 | 32 valuable contributions by Jan M. Sendler <sendler@sendler.de>
|
| /linux-4.4.14/Documentation/scsi/ |
| D | dc395x.txt | 100 reliable driver, there is a chance, that it will kill your valuable data.
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 8.Conclusion | 21 Beyond that, a valuable resource for kernel developers is:
|
| /linux-4.4.14/drivers/net/appletalk/ |
| D | Kconfig | 22 <http://www.tldp.org/docs.html#howto>, contains valuable
|
| /linux-4.4.14/Documentation/RCU/ |
| D | arrayRCU.txt | 20 arrays prove to be particularly valuable (which they have not thus far),
|
| /linux-4.4.14/drivers/mtd/ |
| D | Kconfig | 289 isn't recommended to use with valuable data (anyway if you have
290 valuable data, do backups regardless of software/hardware you
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | nested-vmx.txt | 246 And valuable reviews by:
|
| /linux-4.4.14/Documentation/usb/ |
| D | CREDITS | 118 evaluation boards, specs and valuable advices during
|
| /linux-4.4.14/Documentation/ |
| D | kmemcheck.txt | 90 information from the kmemcheck warnings, which is extremely valuable in
140 any more information (the first report is usually the most valuable
260 The single most valuable information in this report is the RIP (or EIP on 32-
|
| D | edac.txt | 473 necessary handling of errors and might loose valuable information for
|
| D | CodingStyle | 386 because it is a simple way to add valuable information for the reader.
|
| D | SubmittingPatches | 500 Whatever the format, this information provides a valuable help to people
|
| /linux-4.4.14/Documentation/input/ |
| D | input-programming.txt | 133 all the time, or if the device uses a valuable resource (eg. interrupt), it
|
| /linux-4.4.14/arch/mn10300/ |
| D | Kconfig | 259 <http://www.tldp.org/docs.html#howto>, contains valuable
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | compress_offload.txt | 231 - Rakesh Ughreja for valuable feedback
|
| /linux-4.4.14/Documentation/vm/ |
| D | frontswap.txt | 262 page may be taking up valuable real estate. The frontswap_shrink
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-deadline.txt | 486 is a valuable tool, as it can be used to synthetically recreate certain
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | README.OSS | 62 lots of valuable suggestions.
66 Anders Baekgaard Bug hunting and valuable suggestions.
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | cpusets.txt | 87 This can be especially valuable on:
|