Home
last modified time | relevance | path

Searched refs:removal (Results 1 – 92 of 92) sorted by relevance

/linux-4.1.27/drivers/isdn/hardware/eicon/
Ddiddfunc.c32 int removal) in didd_callback() argument
38 if (removal) { in didd_callback()
Didifunc.c158 int removal) in didd_callback() argument
164 if (removal) { in didd_callback()
172 if (removal) { in didd_callback()
Ddadapter.c87 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()
Dmntfunc.c48 int removal) in didd_callback() argument
53 if (removal) { in didd_callback()
63 if (removal) { in didd_callback()
Ddivasfunc.c134 int removal) in didd_callback() argument
142 if (removal) { in didd_callback()
Ddi_defs.h165 …didd_adapter_change_callback_t)(void IDI_CALL_ENTITY_T *context, DESCRIPTOR *adapter, int removal);
Dcapifunc.c1025 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-4.1.27/drivers/staging/sm750fb/
DTODO5 - check on hardware effects of removal of USE_HW_I2C and USE_DVICHIP (these two
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Dsirf-audio.txt14 insertion, removal.
Domap-abe-twl6040.txt16 insertion, removal.
/linux-4.1.27/Documentation/filesystems/
Defivarfs.txt21 as immutable files. This doesn't prevent removal - "chattr -i" will work -
Ddirectory-locking15 3) object removal. Locking rules: caller locks parent, finds victim,
56 (1) if object removal or non-cross-directory rename holds lock on A and
Dceph.txt14 * Automatic rebalancing of data on node addition/removal
Dporting78 Now we have the exclusion between ->lookup() and directory removal (by
464 of course, so they are still serialized wrt removal from inode hash,
Dxfs-delayed-logging-design.txt51 typical example of a rolling transaction is the removal of extents from an
53 of reservation size limitations. Hence a rolling extent removal transaction
55 removal operation. This keeps them moving forward in the log as the operation
Dpath-lookup.txt101 will happen to an object is insertion, and then eventually removal from the
Drelay.txt203 filesystem's directory removal functions should be used for that,
/linux-4.1.27/drivers/of/unittest-data/
Dtests-overlay.dtsi185 /* test overlays application and removal in sequence */
203 /* test overlays application and removal in bad sequence */
/linux-4.1.27/Documentation/networking/
Dsctp.txt25 module removal of lksctp is not yet a safe activity.
Dnfc.txt83 * NFC_EVENT_DEVICE_REMOVED - reports an NFC device removal
Deql.txt261 cleanly in newer kernels because of the removal of the old "slave-
Dcan.txt983 removal of vcan network devices can be managed with the ip(8) tool:
/linux-4.1.27/Documentation/filesystems/nfs/
Dnfsd-admin-interfaces.txt40 removal of listening sockets, and startup and shutdown of the server.
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-bus-acpi56 Writing 1 to this attribute will trigger hot removal of
Dsysfs-devices-system-cpu44 Description: Dynamic addition and removal of CPU's. This is not hotplug
45 removal, this is meant complete removal/addition of the CPU
Dsysfs-bus-fcoe15 ctlr_destroy: 'FCoE Controller' instance removal interface. Writing a
Dsysfs-bus-iio77 Raw (unscaled no bias removal etc.) voltage measurement from
100 Raw (unscaled no bias removal etc.) current measurement from
134 Raw (unscaled no bias removal etc.) temperature measurement.
/linux-4.1.27/drivers/staging/iio/Documentation/
Dring.txt30 If possible, get the most recent scan from the buffer (without removal).
Dinkernel.txt33 on to the core via a call to iio_map_array_register. On removal,
/linux-4.1.27/drivers/staging/media/lirc/
DTODO.lirc_zilog13 lirc_zilog to prevent removal of lirc_zilog when the /dev/lircN device node
/linux-4.1.27/Documentation/RCU/
DwhatisRCU.txt50 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 …]
Drcuref.txt109 until after a grace period has elapsed following removal. This means that
DRTFP.txt1185 ,Title="{[PATCH 1/3] RCU: \url{rcu_assign_pointer()} removal of memory barriers}"
/linux-4.1.27/Documentation/ABI/stable/
Dsysfs-transport-srp14 Zero means immediate removal. Setting this attribute to "off"
/linux-4.1.27/Documentation/
Drobust-futex-ABI.txt67 the address of the 'lock entry', during list insertion and removal,
135 protocol on 'lock entry' insertion and removal:
145 On removal:
Drfkill.txt93 and removal. The API is a simple read/write API that is defined in
Dvolatile-considered-harmful.txt80 keyword to asm statements will prevent this removal.
Deisa.txt114 discovery and removal (note that the .remove function is only called
Dcpu-hotplug.txt28 node insertion and removal require support for CPU hotplug.
180 To support physical addition/removal, one would need some BIOS hooks and
Dsysfs-rules.txt47 at device creation and removal
Drbtree.txt306 Insertion/removal are defined using the following augmented callbacks:
Dmemory-hotplug.txt117 - To enable memory removal, the followings are also necessary
Dworkqueue.txt157 functions are deprecated and scheduled for removal. alloc_workqueue()
Dkobject.txt388 Kobject removal
Ddevices.txt27 removal once kernel version 2.6 (or equivalent) is released. Some of these
914 removal of a driver with this number should not cause
/linux-4.1.27/Documentation/pcmcia/
Ddriver-changes.txt131 * device list iteration upon module removal (as of 2.6.10)
133 client list and call the ->detach() function upon module removal.
/linux-4.1.27/drivers/atm/
Dnicstarmac.copyright7 * interrupts us (except possibly for removal/insertion of the cable?)
DKconfig196 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-4.1.27/Documentation/acpi/
Dgpio-properties.txt94 routine. On removal, the driver should unregister its GPIO mapping table by
/linux-4.1.27/Documentation/powerpc/
Dptrace.txt86 request to ask for its removal. Return -ENOSPC if the requested breakpoint
Dhvcs.txt287 Additionally, disconnecting a vty-server and vty only on module removal or
288 adapter removal is impractical because other vty-servers in other
/linux-4.1.27/Documentation/hwmon/
Dhwmon-kernel-api.txt61 hwmon device does not have to be removed explicitly by the removal function.
/linux-4.1.27/Documentation/s390/
Ddriver-model.txt133 remove: This function is called by the device layer upon removal of the driver,
218 not need to implement anything beyond normal removal routines).
/linux-4.1.27/Documentation/filesystems/pohmelfs/
Ddesign_notes.txt51 removal of objects and data writing are asynchronous and are sent to
/linux-4.1.27/Documentation/power/
Dpm_qos_interface.txt52 Will remove the element. After removal it will update the aggregate target and
123 Will remove the element. After removal it will update the aggregate target and
Ddevices.txt74 or removal (for PCMCIA, MMC/SD, USB, and so on).
452 where common Linux platforms will see such removal. Details of how drivers
Druntime_pm.txt579 removal of their drivers.
/linux-4.1.27/drivers/media/pci/ttpci/
DKconfig151 Firmware can be loaded by insertion and removal of
/linux-4.1.27/Documentation/trace/
Dtracepoints.txt98 probe call, make sure that probe removal and module unload are safe.
/linux-4.1.27/Documentation/usb/
Derror-codes.txt140 device removal events immediately.
Dmass-storage.txt163 host). It may fail, however, if host disallowed medium removal
/linux-4.1.27/Documentation/gpio/
Dgpio.txt64 MMC/SD card insertion/removal, detecting card write-protect status, driving
Dgpio-legacy.txt51 MMC/SD card insertion/removal, detecting card writeprotect status, driving
/linux-4.1.27/arch/ia64/
DKconfig386 bool "Support removal of Bootstrap Processor"
390 Say Y here if your platform SAL will support removal of BSP with HOTPLUG_CPU
/linux-4.1.27/Documentation/vm/
Dcleancache.txt223 file removal or truncation operations either go through VFS or
252 useful if the pages survive inode cache removal.
/linux-4.1.27/Documentation/video4linux/
Dsoc-camera.txt39 mx1_camera.c (broken, scheduled for removal), mx2_camera.c, mx3_camera.c,
/linux-4.1.27/Documentation/fb/
Dsstfb.txt66 Module removal:
Dviafb.txt231 and removal of devices. So a prefix '+' adds the devices from your list
/linux-4.1.27/Documentation/cgroups/
Dmemcg_test.txt15 Allocated at boot or memory hotplug. Freed at memory hot removal.
Dcgroups.txt292 removal of abandoned cgroups. The default value of
569 cgroup removal will proceed to the next step - css_free(). After this
Dmemory.txt453 Charges recorded in swap information is not updated at removal of cgroup.
/linux-4.1.27/net/mac80211/
DKconfig164 debugging messages for station addition/removal.
/linux-4.1.27/tools/perf/Documentation/
Dperf-probe.txt103 adding and removal operations.
/linux-4.1.27/fs/affs/
DChanges66 - locking fixes for link creation/removal.
/linux-4.1.27/Documentation/scsi/
Dtmscsim.txt128 * Support for dyn. addition/removal of devices via add/remove-single-device
230 removal or the addition of a device's DCB and a SCSI register dump.
Dscsi_mid_low_api.txt214 detects the removal of a SCSI device can instigate its removal from
344 make their future removal easier, for example:
601 * the removal of that scsi device. If successful this call will
Dscsi_fc_transport.txt416 removal. If the LLDD delete request fails, the vport object will remain,
DChangeLog.sym53c8xx410 the support of non compliant SCSI removal, insertion and all
DChangeLog.lpfc399 * Janitorial cleanup after removal of sliinit and ringinit[] ring
1196 * Fixed some discovery problems: Introduced deferred ndlp removal
DChangeLog.1992-19971885 media removal prevented. Add another signature for flopticals.
/linux-4.1.27/Documentation/sound/alsa/soc/
DDPCM.txt91 1) Machine driver receives Jack removal event.
/linux-4.1.27/Documentation/timers/
Dhighres.txt239 frequency profiling, and a complete removal of jiffies in the future.
/linux-4.1.27/drivers/net/wan/
DKconfig301 the driver will make use of this feature before module removal
/linux-4.1.27/sound/oss/
DCHANGELOG323 some click removal etc.
/linux-4.1.27/Documentation/arm/
Dcluster-pm-race-avoidance.txt391 Choice (a) permits the removal of some latency by avoiding
/linux-4.1.27/Documentation/PCI/
Dpci-error-recovery.txt398 ack'ing of the interrupt (and thus removal of the source) should just
Dpci.txt37 the PCI layer and supports online insertion/removal of devices [thus
/linux-4.1.27/Documentation/laptops/
Dthinkpad-acpi.txt1464 marked for removal.
1473 is deprecated and marked for removal.
/linux-4.1.27/Documentation/sysctl/
Dkernel.txt124 upon memory add/remove or upon ipc namespace creation/removal.
/linux-4.1.27/Documentation/filesystems/caching/
Dnetfs-api.txt92 a particular key - for instance to mirror the removal of an AFS volume.
/linux-4.1.27/drivers/scsi/aic7xxx/
Daic7xxx.seq2041 * removal of the found SCB from the disconnected list.
/linux-4.1.27/net/wireless/
Dnl80211.c2366 struct wireless_dev *wdev, bool removal) in nl80211_send_iface() argument
2372 if (removal) in nl80211_send_iface()