Improved wording of my safety notes

Author: HadrienG2

src/proto/console/gop.rs

@@ -305,10 +305,10 @@ pub enum PixelFormat {
     /// This means you will have to use the `blt` function which will
     /// convert the graphics data to the device's internal pixel format.
     BltOnly,
-    // NOTE: UEFI also defines a PixelFormatMax variant, and states that all
-    //       valid enum values are guaranteed to be smaller. Since that is the
-    //       case, adding a new enum variant would be a breaking change, so it
-    //       is safe to model this C enum as a Rust enum.
+    // SAFETY: UEFI also defines a PixelFormatMax variant, and states that all
+    //         valid enum values are guaranteed to be smaller. Since that is the
+    //         case, adding a new enum variant would be a breaking change, so it
+    //         is safe to model this C enum as a Rust enum.
 }
 
 /// Bitmask used to indicate which bits of a pixel represent a given color.

src/proto/console/serial.rs

@@ -210,9 +210,9 @@ pub enum Parity {
     Mark,
     /// Space parity
     Space,
-    // NOTE: The serial protocol is very old, and new parity modes are very
-    //       unlikely to be added at this point in time. Therefore, modeling
-    //       this C enum as a Rust enum seems safe.
+    // SAFETY: The serial protocol is very old, and new parity modes are very
+    //         unlikely to be added at this point in time. Therefore, modeling
+    //         this C enum as a Rust enum seems safe.
 }
 
 /// Number of stop bits per character.
@@ -227,7 +227,7 @@ pub enum StopBits {
     OneFive,
     /// 2 stop bits
     Two,
-    // NOTE: The serial protocol is very old, and new stop bit modes are very
-    //       unlikely to be added at this point in time. Therefore, modeling
-    //       this C enum as a Rust enum seems safe.
+    // SAFETY: The serial protocol is very old, and new stop bit modes are very
+    //         unlikely to be added at this point in time. Therefore, modeling
+    //         this C enum as a Rust enum seems safe.
 }

src/table/boot.rs

@@ -390,10 +390,10 @@ pub enum Tpl {
     ///
     /// Even processor interrupts are disable at this level.
     HighLevel = 31,
-    // NOTE: The UEFI specification repeatedly states that only the these
-    //       priority levels may be used, the rest being reserved for internal
-    //       firmware use. So only these priority levels should be exposed to
-    //       the application, and modeling them as a Rust enum seems safe.
+    // SAFETY: The UEFI specification repeatedly states that only the these
+    //         priority levels may be used, the rest being reserved for internal
+    //         firmware use. So only these priority levels should be exposed to
+    //         the application, and modeling them as a Rust enum seems safe.
 }
 
 /// Type of allocation to perform.
@@ -447,9 +447,9 @@ pub enum MemoryType {
     PalCode,
     /// Memory region which is usable and is also non-volatile.
     PersistentMemory,
-    // NOTE: UEFI defines a MaxMemoryType, therefore adding new memory types
-    //       would be a breaking change, so exposing them as a Rust enum seems
-    //       to be safe.
+    // SAFETY: UEFI defines a MaxMemoryType, therefore adding new memory types
+    //         would be a breaking change, and exposing them as a Rust enum
+    //         seems to be safe.
 }
 
 /// A structure describing a region of memory.

src/table/runtime.rs

@@ -49,7 +49,7 @@ pub enum ResetType {
     /// The additional data must be a pointer to
     /// a null-terminated string followed by an UUID.
     PlatformSpecific,
-    // NOTE: This enum is never exposed to the user, but only fed as input to
-    //       the firmware. Therefore, unexpected values can never come from the
-    //       firmware, and modeling this as a Rust enum seems safe.
+    // SAFETY: This enum is never exposed to the user, but only fed as input to
+    //         the firmware. Therefore, unexpected values can never come from
+    //         the firmware, and modeling this as a Rust enum seems safe.
 }