Searched refs:safety (Results 1 – 25 of 28) sorted by relevance
12
/linux-3.4.99/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-3.4.99/arch/x86/include/asm/ |
D | suspend_32.h | 23 unsigned long safety; member
|
D | suspend_64.h | 37 unsigned long safety; member
|
/linux-3.4.99/Documentation/devicetree/bindings/ |
D | eeprom.txt | 17 may result in data loss! If not specified, a safety value of
|
/linux-3.4.99/drivers/media/video/saa7164/ |
D | saa7164-cmd.c | 354 int safety = 0; in saa7164_cmd_send() local 464 if (safety++ > 16) { in saa7164_cmd_send()
|
/linux-3.4.99/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-3.4.99/Documentation/filesystems/ |
D | ocfs2.txt | 73 will hurt performance, but it's good for data-safety.
|
D | ext3.txt | 56 will hurt performance, but it's good for data-safety.
|
D | ext4.txt | 112 after filesystem is first mounted is required for safety) 178 will hurt performance, but it's good for data-safety.
|
D | vfs.txt | 960 appropriate SMP safety is used. CAUTION : d_path() logic is quite
|
/linux-3.4.99/drivers/net/wan/ |
D | farsync.c | 952 int safety; in fst_issue_cmd() local 958 safety = 0; in fst_issue_cmd() 965 if (++safety > 2000) { in fst_issue_cmd() 972 if (safety > 0) { in fst_issue_cmd() 973 dbg(DBG_CMD, "Mailbox clear after %d jiffies\n", safety); in fst_issue_cmd()
|
/linux-3.4.99/Documentation/i2c/busses/ |
D | i2c-parport | 85 the i2c-parport module might be a good safety since data line state
|
/linux-3.4.99/Documentation/laptops/ |
D | thinkpad-acpi.txt | 564 wake up caused by the firmware will have negated most safety nets... 691 CAP_SYS_ADMIN capability for safety reasons, as it can interact badly 1199 safety reasons. To enable them, the module parameter "fan_control=1" 1257 120 seconds. This functionality is called fan safety watchdog. 1298 To program the safety watchdog, use the "watchdog" command. 1307 part, and the exception is the fan safety watchdog. 1347 Fan safety watchdog timer interval, in seconds. Minimum is
|
/linux-3.4.99/Documentation/ |
D | kprobes.txt | 183 Before optimizing a probe, Kprobes performs the following safety checks: 235 rather, it calls synchronize_sched() for safety first, because it's 261 (**)This optimization-safety checking may be replaced with the
|
D | atomic_ops.txt | 411 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
|
D | SubmittingPatches | 686 They provide type safety, have no length limitations, no formatting
|
/linux-3.4.99/arch/sh/kernel/cpu/sh5/ |
D | entry.S | 619 ori r18, 1, r18 ! for safety (do we need this?) 636 synco ! for safety
|
/linux-3.4.99/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-3.4.99/drivers/block/ |
D | Kconfig | 210 you care for the safety of the data in your virtual machine, Y is a
|
/linux-3.4.99/Documentation/networking/ |
D | ppp_generic.txt | 191 SMP safety
|
/linux-3.4.99/Documentation/development-process/ |
D | 4.Coding | 109 multiple evaluation of expressions with side effects and no type safety.
|
12