Searched refs:CHANGE (Results 1 – 10 of 10) sorted by relevance
31 3. CHANGE33 The CHANGE uevent is used in two places. One is when reporting the38 The other CHANGE uevent is used to inform of the completion47 Because the CHANGE uevent was used (in early versions of gfs_controld)
13 event with ACTION=CHANGE is emitted on behalf of the corresponding24 notifications enabled, a udev event with ACTION=CHANGE is emitted.
4 Description: qla2xxx-udev.sh currently looks for uevent CHANGE events to
43 two :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` events with119 - The new adapter state as sent by the :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>`137 * .. _`CEC-EVENT-STATE-CHANGE`:
58 A :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` event is sent when the physical address
60 A :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` event is sent when the
1086 CHANGE in aac_handle_aif() enumerator1148 dev->fsa_dev[container].config_needed = CHANGE; in aac_handle_aif()1219 dev->fsa_dev[container].config_needed = CHANGE; in aac_handle_aif()1447 case CHANGE: in aac_handle_aif()
46 the Netchip vendor id 0x0525. YOU MUST CHANGE TO YOUR OWN VENDOR ID
768 and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
1579 N(UP) N(DOWN) N(REBOOT) N(CHANGE) N(REGISTER) N(UNREGISTER) in netdev_cmd_to_name()
