File tree Expand file tree Collapse file tree 1 file changed +6
-6
lines changed Expand file tree Collapse file tree 1 file changed +6
-6
lines changed Original file line number Diff line number Diff line change @@ -245,11 +245,11 @@ pub(crate) fn memory_map_size() -> MemoryMapMeta {
245
245
}
246
246
247
247
/// Stores the current UEFI memory map in an UEFI-heap allocated buffer
248
- /// and returns a [`MemoryMapOwned`].
249
- ///
248
+ /// and returns a [`MemoryMapOwned`].
249
+ ///
250
250
/// The implementation tries to mitigate some UEFI pitfalls, such as getting
251
251
/// the right allocation size for the memory map to prevent
252
- /// [`Status::BUFFER_TOO_SMALL`].
252
+ /// [`Status::BUFFER_TOO_SMALL`].
253
253
///
254
254
/// # Parameters
255
255
///
@@ -261,15 +261,15 @@ pub(crate) fn memory_map_size() -> MemoryMapMeta {
261
261
///
262
262
/// * [`Status::INVALID_PARAMETER`]: Invalid [`MemoryType`]
263
263
/// * [`Status::OUT_OF_RESOURCES`]: allocation failed.
264
- ///
264
+ ///
265
265
/// # Panics
266
- ///
266
+ ///
267
267
/// Panics if the memory map can't be retrieved.
268
268
pub fn memory_map ( mt : MemoryType ) -> Result < MemoryMapOwned > {
269
269
let mut buffer = MemoryMapBackingMemory :: new ( mt) ?;
270
270
271
271
let meta = get_memory_map ( buffer. as_mut_slice ( ) ) ;
272
-
272
+
273
273
if let Err ( e) = & meta {
274
274
// We don't want to confuse users and let them think they should handle
275
275
// this, as they can't do anything about it anyway.
You can’t perform that action at this time.
0 commit comments