| /linux-4.1.27/arch/arm/mm/ |
| D | proc-sa110.S | 98 mov r0, r0 @ safety
99 mov r0, r0 @ safety
100 mov r0, r0 @ safety
102 mov r0, r0 @ safety
103 mov r0, r0 @ safety
104 mov r0, r0 @ safety
|
| D | proc-sa1100.S | 114 mov r0, r0 @ safety
|
| /linux-4.1.27/arch/x86/include/asm/ |
| D | suspend_32.h | 23 unsigned long safety; member
|
| D | suspend_64.h | 36 unsigned long safety; member
|
| /linux-4.1.27/Documentation/devicetree/bindings/ |
| D | eeprom.txt | 17 may result in data loss! If not specified, a safety value of
|
| /linux-4.1.27/arch/powerpc/boot/dts/ |
| D | ac14xx.dts | 49 0x5 0x0 0xe0400000 0x00010000 /* CS5: safety */
129 safety@5,0 {
130 compatible = "ifm,safety";
|
| /linux-4.1.27/net/hsr/ |
| D | Kconfig | 25 relying on this code in a safety critical system!
|
| /linux-4.1.27/drivers/media/pci/saa7164/ |
| D | saa7164-cmd.c | 354 int safety = 0; in saa7164_cmd_send() local
464 if (safety++ > 16) { in saa7164_cmd_send()
|
| /linux-4.1.27/Documentation/driver-model/ |
| D | bus.txt | 52 type-safety.
|
| D | driver.txt | 49 sacrifice type-safety, so we keep bus-specific structures around.
|
| D | porting.txt | 119 This allows the compiler to verify type-safety of the operations
|
| /linux-4.1.27/drivers/net/wan/ |
| D | farsync.c | 945 int safety; in fst_issue_cmd() local
951 safety = 0; in fst_issue_cmd()
958 if (++safety > 2000) { in fst_issue_cmd()
965 if (safety > 0) { in fst_issue_cmd()
966 dbg(DBG_CMD, "Mailbox clear after %d jiffies\n", safety); in fst_issue_cmd()
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | ocfs2.txt | 73 will hurt performance, but it's good for data-safety.
|
| D | ext3.txt | 57 will hurt performance, but it's good for data-safety.
|
| D | ext4.txt | 112 after filesystem is first mounted is required for safety)
179 will hurt performance, but it's good for data-safety.
|
| D | vfs.txt | 1014 appropriate SMP safety is used. CAUTION : d_path() logic is quite
|
| /linux-4.1.27/Documentation/i2c/busses/ |
| D | i2c-parport | 85 the i2c-parport module might be a good safety since data line state
|
| /linux-4.1.27/Documentation/laptops/ |
| D | thinkpad-acpi.txt | 547 wake up caused by the firmware will have negated most safety nets...
630 CAP_SYS_ADMIN capability for safety reasons, as it can interact badly
1141 safety reasons. To enable them, the module parameter "fan_control=1"
1199 120 seconds. This functionality is called fan safety watchdog.
1240 To program the safety watchdog, use the "watchdog" command.
1249 part, and the exception is the fan safety watchdog.
1289 Fan safety watchdog timer interval, in seconds. Minimum is
|
| /linux-4.1.27/drivers/thermal/ |
| D | Kconfig | 273 CPU/SOC, for thermal safety reasons.
|
| /linux-4.1.27/Documentation/ |
| D | kprobes.txt | 184 Before optimizing a probe, Kprobes performs the following safety checks:
236 rather, it calls synchronize_sched() for safety first, because it's
262 (**)This optimization-safety checking may be replaced with the
|
| D | atomic_ops.txt | 410 as a spinlock for SMP safety. Sparc32 lacked a "compare and swap"
|
| D | edac.txt | 46 continue to operate, but with less safety. Preventive maintenance and
|
| /linux-4.1.27/arch/sh/kernel/cpu/sh5/ |
| D | entry.S | 619 ori r18, 1, r18 ! for safety (do we need this?)
636 synco ! for safety
|
| /linux-4.1.27/Documentation/ioctl/ |
| D | botching-up-ioctls.txt | 113 still too tricky have a timeout or hangcheck safety net as a last-ditch
|
| /linux-4.1.27/Documentation/locking/ |
| D | ww-mutex-design.txt | 69 interface safety:
|
| /linux-4.1.27/Documentation/networking/ |
| D | filter.txt | 832 is deterministic and the kernel can easily prove that. The safety of the program
1007 The safety of the eBPF program is determined in two steps.
1088 from safety point of view. The verifier will guarantee that the function is
|
| D | ppp_generic.txt | 191 SMP safety
|
| /linux-4.1.27/scripts/ |
| D | spelling.txt | 844 safty||safety
|
| /linux-4.1.27/Documentation/scsi/ |
| D | ChangeLog.lpfc | 1079 * Free SCSI buf safety memory pool on shutdown to eliminate memory
1114 * Added scsi_buf safety pool to address scsi_buf failures in
1117 comes from the safety pool.
1238 * Fix misspelled word "safety" in function names.
1574 * Added code for safety pools for following objects: mbuf/bpl,
|
| /linux-4.1.27/Documentation/arm/ |
| D | cluster-pm-race-avoidance.txt | 41 lightweight as possible, while providing the required safety properties.
|
| /linux-4.1.27/drivers/block/ |
| D | Kconfig | 203 you care for the safety of the data in your virtual machine, Y is a
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 4.Coding | 109 multiple evaluation of expressions with side effects and no type safety.
|
| /linux-4.1.27/drivers/scsi/ |
| D | Kconfig | 1222 This option is only provided for safety if you suspect some SCSI
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | api.txt | 3366 safety mechanism, and should be set to the size in bytes of the memory that
|
| /linux-4.1.27/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 1980 uml_moo creates a new backing file by default as a safety measure. It
|