/linux-3.4.99/drivers/isdn/hardware/eicon/ |
D | diddfunc.c | 32 int removal) in didd_callback() argument 38 if (removal) { in didd_callback()
|
D | idifunc.c | 158 int removal) in didd_callback() argument 164 if (removal) { in didd_callback() 172 if (removal) { in didd_callback()
|
D | dadapter.c | 87 static void diva_notify_adapter_change(DESCRIPTOR *d, int removal); 309 static void diva_notify_adapter_change(DESCRIPTOR *d, int removal) { in diva_notify_adapter_change() argument 322 (*(nfy.callback))(nfy.context, d, removal); in diva_notify_adapter_change()
|
D | mntfunc.c | 48 int removal) in didd_callback() argument 53 if (removal) { in didd_callback() 63 if (removal) { in didd_callback()
|
D | divasfunc.c | 134 int removal) in didd_callback() argument 142 if (removal) { in didd_callback()
|
D | di_defs.h | 165 …didd_adapter_change_callback_t)(void IDI_CALL_ENTITY_T *context, DESCRIPTOR *adapter, int removal);
|
D | capifunc.c | 1025 static void didd_callback(void *context, DESCRIPTOR *adapter, int removal) in didd_callback() argument 1031 if (removal) { in didd_callback() 1039 if (removal) { in didd_callback()
|
/linux-3.4.99/Documentation/ABI/testing/ |
D | sysfs-devices-system-cpu | 69 Description: Dynamic addition and removal of CPU's. This is not hotplug 70 removal, this is meant complete removal/addition of the CPU
|
/linux-3.4.99/Documentation/networking/ |
D | sctp.txt | 26 module removal of lksctp is not yet a safe activity.
|
D | nfc.txt | 83 * NFC_EVENT_DEVICE_REMOVED - reports an NFC device removal
|
/linux-3.4.99/drivers/pci/hotplug/ |
D | Kconfig | 32 This is a "logical" removal, not a physical or electrical 33 removal.
|
/linux-3.4.99/drivers/staging/iio/Documentation/ |
D | ring.txt | 30 If possible, get the most recent scan from the buffer (without removal).
|
D | inkernel.txt | 33 on to the core via a call to iio_map_array_register. On removal,
|
/linux-3.4.99/drivers/staging/media/lirc/ |
D | TODO.lirc_zilog | 13 lirc_zilog to prevent removal of lirc_zilog when the /dev/lircN device node
|
/linux-3.4.99/Documentation/RCU/ |
D | whatisRCU.txt | 50 The basic idea behind RCU is to split updates into "removal" and 51 "reclamation" phases. The removal phase removes references to data items 54 The reason that it is safe to run the removal phase concurrently with 59 removal phase. Because reclaiming data items can disrupt any readers 63 Splitting the update into removal and reclamation phases permits the 64 updater to perform the removal phase immediately, and to defer the 65 reclamation phase until all readers active during the removal phase have 68 during the removal phase need be considered, because any reader starting 69 after the removal phase will be unable to gain a reference to the removed 93 pointers are atomic on modern CPUs, allowing atomic insertion, removal, [all …]
|
/linux-3.4.99/drivers/net/wireless/ |
D | Kconfig | 160 the scheduled removal of this driver on the kernel see the feature 161 removal schedule: 163 Documentation/feature-removal-schedule.txt
|
/linux-3.4.99/Documentation/power/ |
D | pm_qos_interface.txt | 50 Will remove the element. After removal it will update the aggregate target and 115 Will remove the element. After removal it will update the aggregate target and
|
/linux-3.4.99/Documentation/filesystems/ |
D | directory-locking | 11 3) object removal. Locking rules: caller locks parent, finds victim, 49 (1) if object removal or non-cross-directory rename holds lock on A and
|
/linux-3.4.99/Documentation/ |
D | robust-futex-ABI.txt | 67 the address of the 'lock entry', during list insertion and removal, 135 protocol on 'lock entry' insertion and removal: 145 On removal:
|
/linux-3.4.99/Documentation/pcmcia/ |
D | driver-changes.txt | 131 * device list iteration upon module removal (as of 2.6.10) 133 client list and call the ->detach() function upon module removal.
|
/linux-3.4.99/drivers/atm/ |
D | nicstarmac.copyright | 7 * interrupts us (except possibly for removal/insertion of the cable?)
|
D | Kconfig | 196 removal and reinsertion and provides some statistics. This driver 197 doesn't have removal capability when compiled as a module, so if you 206 addition to cable removal/reinsertion detection, this driver allows
|
/linux-3.4.99/sound/ |
D | Kconfig | 55 Please read Documentation/feature-removal-schedule.txt for
|
/linux-3.4.99/Documentation/ABI/ |
D | README | 39 The file Documentation/feature-removal-schedule.txt may describe
|
/linux-3.4.99/scripts/ |
D | checkpatch.pl | 357 my $removal = "Documentation/feature-removal-schedule.txt"; 358 if ($tree && -f "$root/$removal") { 359 open(my $REMOVE, '<', "$root/$removal") || 360 die "$P: $removal: open failed - $!\n";
|