Searched refs:removal (Results 1 – 25 of 127) sorted by relevance
123456
| /Linux-v6.6/drivers/staging/media/deprecated/atmel/ |
| D | Kconfig | 21 This driver is deprecated and is scheduled for removal by
40 This driver is deprecated and is scheduled for removal by
|
| /Linux-v6.6/drivers/staging/media/ |
| D | Kconfig | 48 scheduled for future removal from the kernel.
50 If you wish to work on these drivers to prevent their removal,
|
| /Linux-v6.6/drivers/of/unittest-data/ |
| D | overlay_6.dtso | 6 /* overlays 6, 7 application and removal in sequence */
|
| D | overlay_7.dtso | 6 /* overlays 6, 7 application and removal in sequence */
|
| D | overlay_8.dtso | 6 /* overlays 8, 9, 10, 11 application and removal in bad sequence */
|
| D | overlay_9.dtso | 6 /* overlays 8, 9, 10, 11 application and removal in bad sequence */
|
| D | overlay_10.dtso | 6 /* overlays 8, 9, 10, 11 application and removal in bad sequence */
|
| D | overlay_11.dtso | 6 /* overlays 8, 9, 10, 11 application and removal in bad sequence */
|
| /Linux-v6.6/drivers/staging/sm750fb/ |
| D | TODO | 6 - check on hardware effects of removal of USE_HW_I2C and USE_DVICHIP (these two
|
| /Linux-v6.6/Documentation/devicetree/bindings/sound/ |
| D | sirf-audio.txt | 14 insertion, removal.
|
| D | omap-abe-twl6040.txt | 16 insertion, removal.
|
| /Linux-v6.6/drivers/staging/ks7010/ |
| D | TODO | 27 - fix the 'card removal' event when card is inserted when booting
|
| /Linux-v6.6/Documentation/filesystems/ |
| D | efivarfs.rst | 24 as immutable files. This doesn't prevent removal - "chattr -i" will work -
|
| /Linux-v6.6/Documentation/networking/ |
| D | sctp.rst | 30 module removal of lksctp is not yet a safe activity.
|
| /Linux-v6.6/drivers/net/wireless/intel/iwlwifi/pcie/ |
| D | trans.c | 2104 struct iwl_trans_pcie_removal *removal = in iwl_trans_pcie_removal_wk() local
2106 struct pci_dev *pdev = removal->pdev; in iwl_trans_pcie_removal_wk()
2115 if (removal->rescan) in iwl_trans_pcie_removal_wk()
2119 kfree(removal); in iwl_trans_pcie_removal_wk()
2125 struct iwl_trans_pcie_removal *removal; in iwl_trans_pcie_remove() local
2144 removal = kzalloc(sizeof(*removal), GFP_ATOMIC); in iwl_trans_pcie_remove()
2145 if (!removal) { in iwl_trans_pcie_remove()
2155 removal->pdev = to_pci_dev(trans->dev); in iwl_trans_pcie_remove()
2156 removal->rescan = rescan; in iwl_trans_pcie_remove()
2157 INIT_WORK(&removal->work, iwl_trans_pcie_removal_wk); in iwl_trans_pcie_remove()
[all …]
|
| /Linux-v6.6/Documentation/admin-guide/nfs/ |
| D | nfsd-admin-interfaces.rst | 39 removal of listening sockets, and startup and shutdown of the server.
|
| /Linux-v6.6/Documentation/sound/designs/ |
| D | jack-controls.rst | 21 intelligently based on jack insertion or removal events.
|
| /Linux-v6.6/Documentation/driver-api/soundwire/ |
| D | locking.rst | 20 - Addition and removal of Slave(s), changing Slave status.
|
| /Linux-v6.6/drivers/staging/iio/Documentation/ |
| D | inkernel.txt | 33 on to the core via a call to iio_map_array_register. On removal,
|
| /Linux-v6.6/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 37 # obvious that an easy to solution to this problem should just be the removal
|
| /Linux-v6.6/Documentation/translations/ |
| D | index.rst | 44 English documentation. Any content addition, removal or update, must be
|
| /Linux-v6.6/Documentation/pcmcia/ |
| D | driver-changes.rst | 139 * device list iteration upon module removal (as of 2.6.10)
141 client list and call the ->detach() function upon module removal.
|
| /Linux-v6.6/Documentation/locking/ |
| D | robust-futex-ABI.rst | 69 the address of the 'lock entry', during list insertion and removal,
137 protocol on 'lock entry' insertion and removal:
148 On removal:
|
| /Linux-v6.6/Documentation/ABI/stable/ |
| D | sysfs-transport-srp | 14 Zero means immediate removal. Setting this attribute to "off"
|
| /Linux-v6.6/Documentation/RCU/ |
| D | whatisRCU.rst | 76 The basic idea behind RCU is to split updates into "removal" and
77 "reclamation" phases. The removal phase removes references to data items
80 The reason that it is safe to run the removal phase concurrently with
85 removal phase. Because reclaiming data items can disrupt any readers
89 Splitting the update into removal and reclamation phases permits the
90 updater to perform the removal phase immediately, and to defer the
91 reclamation phase until all readers active during the removal phase have
94 during the removal phase need be considered, because any reader starting
95 after the removal phase will be unable to gain a reference to the removed
119 pointers are atomic on modern CPUs, allowing atomic insertion, removal,
[all …]
|
123456
