/linux-3.4.99/fs/ocfs2/dlm/ |
D | dlmunlock.c | 62 int *actions); 67 int *actions); 106 int actions = 0; in dlmunlock_common() local 156 status = dlm_get_cancel_actions(dlm, res, lock, lksb, &actions); in dlmunlock_common() 158 status = dlm_get_unlock_actions(dlm, res, lock, lksb, &actions); in dlmunlock_common() 189 actions &= ~(DLM_UNLOCK_REMOVE_LOCK| in dlmunlock_common() 204 actions = 0; in dlmunlock_common() 217 if (actions & DLM_UNLOCK_REMOVE_LOCK) { in dlmunlock_common() 221 if (actions & DLM_UNLOCK_REGRANT_LOCK) { in dlmunlock_common() 225 if (actions & DLM_UNLOCK_CLEAR_CONVERT_TYPE) { in dlmunlock_common() [all …]
|
/linux-3.4.99/arch/parisc/kernel/ |
D | processor.c | 201 struct irqaction actions[]; in processor_probe() 207 actions = kmalloc(sizeof(struct irqaction)*MAX_CPU_IRQ, GFP_ATOMIC); in processor_probe() 208 if (!actions) { in processor_probe() 210 actions = cpu_irq_actions[0]; in processor_probe() 213 cpu_irq_actions[cpuid] = actions; in processor_probe()
|
/linux-3.4.99/Documentation/networking/ |
D | tc-actions-env-rules.txt | 2 The "environmental" rules for authors of any new tc actions are: 23 The "environmental" rules for callers of actions (qdiscs etc) are:
|
D | openvswitch.txt | 14 on packet headers and metadata to sets of actions. The most common 15 action forwards the packet to another vport; other actions are also 20 is a matching flow, it executes the associated actions. If there is
|
D | 00-INDEX | 193 tc-actions-env-rules.txt 194 - rules for traffic control (tc) actions.
|
D | smctr.txt | 39 the appropriate actions.
|
/linux-3.4.99/net/openvswitch/ |
D | Makefile | 8 actions.o \
|
D | datapath.c | 400 const struct nlattr *probability, *actions; in validate_sample() local 418 actions = attrs[OVS_SAMPLE_ATTR_ACTIONS]; in validate_sample() 419 if (!actions || (nla_len(actions) && nla_len(actions) < NLA_HDRLEN)) in validate_sample() 421 return validate_actions(actions, key, depth + 1); in validate_sample() 810 sf_acts->actions); in ovs_flow_cmd_fill_info() 965 memcmp(old_acts->actions, nla_data(acts_attrs), in ovs_flow_cmd_new_or_set()
|
D | flow.h | 40 struct nlattr actions[]; member
|
/linux-3.4.99/Documentation/usb/ |
D | hotplug.txt | 17 be driver-specific actions. 19 This involves a mix of kernel mode and user mode actions. Making devices 20 be immediately usable means that any user mode actions can't wait for an 25 Those triggered actions must support a system's administrative policies; 29 Because some of those actions rely on information about drivers (metadata)
|
/linux-3.4.99/Documentation/scsi/ |
D | scsi_eh.txt | 151 We'll talk about how SCSI EH takes actions to abort - make LLDD 157 LLDD's can implement SCSI EH actions in one of the following two 196 To achieve these goals, EH performs recovery actions with increasing 197 severity. Some actions are performed by issuing SCSI commands and 207 Higher-severity actions are taken only when lower-severity actions 214 - Recovery actions are performed on failed scmds on the to do list, 222 - Higher severity actions are taken iff eh_work_q is not empty after 223 lower severity actions are complete. 331 higher-severity actions.
|
/linux-3.4.99/Documentation/isdn/ |
D | README.hysdn | 165 0x00000040 Log every firmware write actions 170 0x00001000 Log the asynchronous scheduler actions (config and log) 171 0x00100000 Log all open and close actions to /proc/net/hysdn/card files 172 0x00200000 Log all actions from /proc file entries
|
/linux-3.4.99/drivers/net/can/softing/ |
D | Kconfig | 15 As such, some actions (start/stop/busoff recovery) on 1 bus
|
/linux-3.4.99/include/linux/ |
D | ti_wilink_st.h | 307 u8 actions[0]; member
|
/linux-3.4.99/drivers/usb/host/ |
D | ehci.h | 131 unsigned long actions; member 217 clear_bit (action, &ehci->actions); in timer_action_done()
|
D | oxu210hp.h | 419 unsigned long actions; member
|
D | ehci-hcd.c | 142 & ehci->actions)) in timer_action() 145 if (!test_and_set_bit(action, &ehci->actions)) { in timer_action() 452 if (test_bit (TIMER_ASYNC_OFF, &ehci->actions)) in ehci_watchdog()
|
/linux-3.4.99/Documentation/power/ |
D | devices.txt | 365 low-power state. Instead the PM core will unwind its actions by resuming all 375 1. The resume_noirq callback methods should perform any actions needed 377 means undoing the actions of the suspend_noirq phase. If the bus type 387 actions. 390 the resume methods. This generally involves undoing the actions of the 395 undoing the actions of the suspend phase. 397 4. The complete phase should undo the actions of the prepare phase. Note, 476 above. Its methods should undo the actions of the preceding 622 Moreover, the specific actions taken may depend on the target system state. 637 actions that either require user space to be available, or at least won't [all …]
|
/linux-3.4.99/init/ |
D | initramfs.c | 366 static __initdata int (*actions[])(void) = { variable 382 while (!actions[state]()) in write_buffer()
|
/linux-3.4.99/drivers/staging/wlags49_h2/ |
D | README.ubuntu | 87 -- Recovery actions added 100 The last point, recovery actions added, needs some clarification.
|
/linux-3.4.99/Documentation/watchdog/ |
D | convert_drivers_to_kernel_api.txt | 15 Old drivers define their own file_operations for actions like open(), write(), 19 Here is a overview of the functions and probably needed actions:
|
/linux-3.4.99/Documentation/PCI/ |
D | pcieaer-howto.txt | 35 - Performs error recovery actions. 156 when performing error recovery actions. 172 require any recovery actions. The AER driver clears the device's
|
/linux-3.4.99/Documentation/laptops/ |
D | laptop-mode.txt | 706 action=/etc/acpi/actions/ac.sh %e 712 action=/etc/acpi/actions/battery.sh %e 716 ----------------/etc/acpi/actions/ac.sh BEGIN----------------------------------- 733 ---------------------------/etc/acpi/actions/ac.sh END-------------------------- 736 ---------------------------/etc/acpi/actions/battery.sh BEGIN------------------- 775 ---------------------------/etc/acpi/actions/battery.sh END--------------------
|
/linux-3.4.99/drivers/scsi/aic7xxx/ |
D | Kconfig.aic79xx | 42 The bus settle delay following all error recovery actions is
|
/linux-3.4.99/Documentation/ |
D | dcdbas.txt | 5 management interrupts and host control actions (system power cycle or
|