Home
last modified time | relevance | path

Searched refs:safety (Results 1 – 25 of 29) sorted by relevance

12

/linux-2.6.39/arch/arm/mm/
Dproc-sa110.S95 mov r0, r0 @ safety
96 mov r0, r0 @ safety
97 mov r0, r0 @ safety
99 mov r0, r0 @ safety
100 mov r0, r0 @ safety
101 mov r0, r0 @ safety
Dproc-sa1100.S113 mov r0, r0 @ safety
/linux-2.6.39/drivers/staging/intel_sst/
DTODO7 Review the misc device ioctls for 32/64bit safety and sanity
8 Review the misc device ioctls for size safety depending on config and decide
/linux-2.6.39/arch/x86/include/asm/
Dsuspend_32.h25 unsigned long safety; member
Dsuspend_64.h42 unsigned long safety; member
/linux-2.6.39/Documentation/devicetree/bindings/
Deeprom.txt17 may result in data loss! If not specified, a safety value of
/linux-2.6.39/drivers/staging/gma500/
DTODO11 As per kernel policy and the in the interest of the safety of various
/linux-2.6.39/drivers/media/video/saa7164/
Dsaa7164-cmd.c354 int safety = 0; in saa7164_cmd_send() local
464 if (safety++ > 16) { in saa7164_cmd_send()
/linux-2.6.39/Documentation/driver-model/
Dbus.txt69 type-safety.
Ddriver.txt65 sacrifice type-safety, so we keep bus-specific structures around.
Dporting.txt119 This allows the compiler to verify type-safety of the operations
/linux-2.6.39/Documentation/filesystems/
Docfs2.txt67 will hurt performance, but it's good for data-safety.
Dext3.txt56 will hurt performance, but it's good for data-safety.
Dext4.txt112 after filesystem is first mounted is required for safety)
179 will hurt performance, but it's good for data-safety.
/linux-2.6.39/drivers/net/wan/
Dfarsync.c951 int safety; in fst_issue_cmd() local
957 safety = 0; in fst_issue_cmd()
964 if (++safety > 2000) { in fst_issue_cmd()
971 if (safety > 0) { in fst_issue_cmd()
972 dbg(DBG_CMD, "Mailbox clear after %d jiffies\n", safety); in fst_issue_cmd()
/linux-2.6.39/Documentation/i2c/busses/
Di2c-parport85 the i2c-parport module might be a good safety since data line state
/linux-2.6.39/Documentation/laptops/
Dthinkpad-acpi.txt559 wake up caused by the firmware will have negated most safety nets...
686 CAP_SYS_ADMIN capability for safety reasons, as it can interact badly
1194 safety reasons. To enable them, the module parameter "fan_control=1"
1252 120 seconds. This functionality is called fan safety watchdog.
1293 To program the safety watchdog, use the "watchdog" command.
1302 part, and the exception is the fan safety watchdog.
1342 Fan safety watchdog timer interval, in seconds. Minimum is
/linux-2.6.39/Documentation/
Dkprobes.txt183 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
Datomic_ops.txt324 as a spinlock for SMP safety. Sparc32 lacked a "compare and swap"
Dedac.txt46 continue to operate, but with less safety. Preventive maintenance and
/linux-2.6.39/arch/sh/kernel/cpu/sh5/
Dentry.S619 ori r18, 1, r18 ! for safety (do we need this?)
636 synco ! for safety
/linux-2.6.39/Documentation/scsi/
DChangeLog.lpfc1079 * 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-2.6.39/drivers/block/
DKconfig208 you care for the safety of the data in your virtual machine, Y is a
/linux-2.6.39/Documentation/networking/
Dppp_generic.txt191 SMP safety
/linux-2.6.39/Documentation/development-process/
D4.Coding109 multiple evaluation of expressions with side effects and no type safety.

12