From fcf8bdcd5313ae076506cbbf8474bb660fa47a93 Mon Sep 17 00:00:00 2001 From: Laszlo Ersek Date: Sat, 7 Sep 2019 00:58:19 +0200 Subject: SecurityPkg: stop abusing EFI_EVENT for protocol notify registration EfiCreateProtocolNotifyEvent() takes a (VOID**) for "Registration", similarly to gBS->RegisterProtocolNotify(). We should pass the address of an actual pointer-to-VOID, and not the address of an EFI_EVENT. EFI_EVENT just happens to be specified as (VOID*), and has nothing to do with the registration. This change is a no-op in practice; it's a semantic improvement. Cc: Chao Zhang Cc: Jian Wang Cc: Jiewen Yao Signed-off-by: Laszlo Ersek Reviewed-by: Philippe Mathieu-Daude Reviewed-by: Jiewen Yao Reviewed-by: Chao Zhang --- SecurityPkg/HddPassword/HddPasswordDxe.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SecurityPkg/HddPassword/HddPasswordDxe.c b/SecurityPkg/HddPassword/HddPasswordDxe.c index b0d795b659..051e64091d 100644 --- a/SecurityPkg/HddPassword/HddPasswordDxe.c +++ b/SecurityPkg/HddPassword/HddPasswordDxe.c @@ -2770,7 +2770,7 @@ HddPasswordDxeInit ( { EFI_STATUS Status; HDD_PASSWORD_DXE_PRIVATE_DATA *Private; - EFI_EVENT Registration; + VOID *Registration; EFI_EVENT EndOfDxeEvent; EDKII_VARIABLE_LOCK_PROTOCOL *VariableLock; -- cgit v1.2.3