Searched refs:CHANGE (Results 1 – 7 of 7) 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
899 CHANGE in aac_handle_aif() enumerator972 dev->fsa_dev[container].config_needed = CHANGE; in aac_handle_aif()1043 dev->fsa_dev[container].config_needed = CHANGE; in aac_handle_aif()1269 case CHANGE: in aac_handle_aif()
46 the Netchip vendor id 0x0525. YOU MUST CHANGE TO YOUR OWN VENDOR ID
653 and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
28 SECTION 1 - CREATING AND SENDING YOUR CHANGE