Update comments for Protocol definitions to match UEFI spec.

[mirror_edk2.git] / MdePkg / Include / Protocol / Security.h

diff --git a/MdePkg/Include/Protocol/Security.h b/MdePkg/Include/Protocol/Security.h
index 4ab386fd67c680943bbcf791e5307e8d5c90763d..71c236f1511c710e2519665df1a8277cdcdf426c 100644 (file)
--- a/MdePkg/Include/Protocol/Security.h
+++ b/MdePkg/Include/Protocol/Security.h
@@ -89,28 +89,11 @@ EFI_STATUS
   IN  EFI_DEVICE_PATH_PROTOCOL      *File\r
   );\r
 \r
-//\r
-// Interface stucture for the Timer Architectural Protocol\r
-//\r
-/**\r
-  @par Protocol Description:\r
-\r
-  The EFI_SECURITY_ARCH_PROTOCOL is used to abstract platform-specific policy\r
-  from the DXE core.  This includes locking flash upon failure to authenticate, \r
-  attestation logging, and other exception operations.\r
-\r
-  The driver that produces the EFI_SECURITY_ARCH_PROTOCOL may also optionally \r
-  install the EFI_SECURITY_POLICY_PROTOCOL_GUID onto a new handle with a NULL \r
-  interface.  The existence of this GUID in the protocol database means that \r
-  the GUIDed Section Extraction Protocol should authenticate the contents of \r
-  an Authentication Section.  The expectation is that the GUIDed Section \r
-  Extraction protocol will look for the existence of the EFI_SECURITY_POLICY_ \r
-  PROTOCOL_GUID in the protocol database.  If it exists, then the publication \r
-  thereof is taken as an injunction to attempt an authentication of any section \r
-  wrapped in an Authentication Section.  See the Firmware File System \r
-  Specification for details on the GUIDed Section Extraction Protocol and \r
-  Authentication Sections.\r
-**/\r
+///\r
+/// The EFI_SECURITY_ARCH_PROTOCOL is used to abstract platform-specific policy\r
+/// from the DXE core.  This includes locking flash upon failure to authenticate, \r
+/// attestation logging, and other exception operations.\r
+///\r
 struct _EFI_SECURITY_ARCH_PROTOCOL {\r
   EFI_SECURITY_FILE_AUTHENTICATION_STATE  FileAuthenticationState;\r
 };\r