/linux-6.14.4/net/sunrpc/xprtrdma/ |
D | ib_client.c | 45 * rpcrdma_rn_register - register to get device removal notifications 48 * @done: callback to notify caller of device removal 83 * rpcrdma_rn_unregister - stop device removal notifications 126 * rpcrdma_remove_one - ib_client device removal callback
|
/linux-6.14.4/drivers/pps/ |
D | kc.c | 72 /* pps_kc_remove - unbind kernel consumer on PPS source removal 75 * This function is used to disable kernel consumer on PPS source removal 87 " on device removal\n"); in pps_kc_remove()
|
/linux-6.14.4/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-6.14.4/drivers/mmc/host/ |
D | sdhci-bcm-kona.c | 75 * insert-removal. in sdhci_bcm_kona_sd_reset() 100 * insert-removal. in sdhci_bcm_kona_sd_init() 107 * Software emulation of the SD card insertion/removal. Set insert=1 for insert 108 * and insert=0 for removal. The card detection is done by GPIO. For Broadcom 122 * insert-removal. in sdhci_bcm_kona_sd_card_emulate()
|
/linux-6.14.4/include/linux/ |
D | plist.h | 21 * Addition is O(K), removal is O(1), change of priority of a node is 59 * Removal means remove it from the node_list and remove it from 61 * of removal from the prio_list it must be checked whether other 161 * Iterate over a plist of given type, safe against removal of list entry. 194 * Iterate over list of given type, safe against removal of list entry.
|
D | list.h | 718 * list_for_each_safe - iterate over a list safe against removal of list entry 729 * list_for_each_prev_safe - iterate over a list backwards safe against removal of list entry 850 * list_for_each_entry_safe - iterate over list of given type safe against removal of list entry 863 * list_for_each_entry_safe_continue - continue list iteration safe against removal 870 * safe against removal of list entry. 879 * list_for_each_entry_safe_from - iterate over list from current point safe against removal 886 * removal of list entry. 894 * list_for_each_entry_safe_reverse - iterate backwards over list safe against removal 900 * Iterate backwards over list of given type, safe against removal 944 * Not that not all removal functions will leave a node in unhashed [all …]
|
D | list_nulls.h | 63 * Not that not all removal functions will leave a node in unhashed state. 76 * Not that not all removal functions will leave a node in unhashed state.
|
/linux-6.14.4/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-6.14.4/tools/include/linux/ |
D | list.h | 431 * list_for_each_safe - iterate over a list safe against removal of list entry 441 * list_for_each_prev_safe - iterate over a list backwards safe against removal of list entry 525 * list_for_each_entry_safe - iterate over list of given type safe against removal of list entry 538 * list_for_each_entry_safe_continue - continue list iteration safe against removal 545 * safe against removal of list entry. 554 * list_for_each_entry_safe_from - iterate over list from current point safe against removal 561 * removal of list entry. 569 * list_for_each_entry_safe_reverse - iterate backwards over list safe against removal 575 * Iterate backwards over list of given type, safe against removal 750 * hlist_for_each_entry_safe - iterate over list of given type safe against removal of list entry
|
/linux-6.14.4/drivers/gpu/drm/xe/ |
D | xe_ggtt_types.h | 66 /** @delayed_removal_work: The work struct for the delayed removal */ 68 /** @invalidate_on_remove: If it needs invalidation upon removal */
|
/linux-6.14.4/drivers/gpu/drm/i915/gem/ |
D | i915_gem_object_frontbuffer.h | 41 * mechanism is used to handle e.g. ongoing removal of frontbuffer pointer. 79 * mechanism is used to handle e.g. ongoing removal of frontbuffer pointer. This
|
/linux-6.14.4/Documentation/pcmcia/ |
D | driver-changes.rst | 81 * Unify detach and REMOVAL event code, as well as attach and INSERTION 139 * device list iteration upon module removal (as of 2.6.10) 141 client list and call the ->detach() function upon module removal.
|
/linux-6.14.4/drivers/input/mouse/ |
D | psmouse-smbus.c | 144 * This schedules removal of SMBus companion device. We have to do 148 * Note that this may be racing with i2c adapter removal, but we 180 "posting removal request for SMBus companion %s\n", in psmouse_smbus_disconnect()
|
/linux-6.14.4/drivers/base/power/ |
D | qos-test.c | 73 * Test that a freq_qos_request can be added again after removal 76 * QoS requests after removal")
|
/linux-6.14.4/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-6.14.4/drivers/pci/hotplug/ |
D | pciehp_pci.c | 88 * true for safe removal via sysfs or an Attention Button press, 89 * false for surprise removal
|
/linux-6.14.4/drivers/thermal/ |
D | thermal_core.h | 78 * @removal: removal completion 120 struct completion removal; member
|
/linux-6.14.4/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 …]
|
/linux-6.14.4/fs/sysfs/ |
D | dir.c | 84 * In general, kobject owner is responsible for ensuring removal in sysfs_remove_dir() 88 * control over removal. @kobj->sd may be removed anytime in sysfs_remove_dir()
|
/linux-6.14.4/tools/testing/selftests/sgx/ |
D | main.c | 488 /* Complete page removal. */ 1437 /* Start page removal by requesting change of page type to PT_TRIM. */ in TEST_F() 1453 * Enter enclave via TCS #1 and approve page removal by sending in TEST_F() 1493 /* Send final ioctl() to complete page removal. */ in TEST_F() 1557 * Ensure sane behavior if user requests page removal, does not run 1558 * EACCEPT from within enclave but still attempts to finalize page removal 1560 * because the removal was not EACCEPTed from within the enclave. 1638 /* Start page removal by requesting change of page type to PT_TRIM */ in TEST_F() 1655 /* Send final ioctl() to complete page removal */ in TEST_F() 1671 * Request enclave page removal but instead of correctly following with [all …]
|
/linux-6.14.4/Documentation/core-api/ |
D | cpu_hotplug.rst | 19 insertion and removal require support for CPU hotplug. 355 setup and removal. 386 invocations of the state callbacks on add and removal. To set up such a 462 removal, then this number has to be saved by the caller and used 471 Removal of a CPU hotplug state 498 In order to complete the removal, the teardown callback should not fail. 500 The state removal and the callback invocations are serialized against CPU 564 In order to complete the removal, the teardown callback should not fail.
|
/linux-6.14.4/drivers/of/unittest-data/ |
D | overlay_7.dtso | 6 /* overlays 6, 7 application and removal in sequence */
|
D | overlay_6.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 */
|
/linux-6.14.4/drivers/char/tpm/eventlog/ |
D | common.c | 177 * between removal and opening of pseudo files. To handle this, a in tpm_bios_log_teardown() 178 * workaround is added by making i_private = NULL here during removal in tpm_bios_log_teardown()
|