[PATCH] fixup: mm/memory: remove zap_details parameter from zap_page_range_single()

[David Hildenbrand (Arm)]

Signed-off-by: David Hildenbrand (Arm) <david at kernel.org>
---
 rust/kernel/mm/virt.rs | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/rust/kernel/mm/virt.rs b/rust/kernel/mm/virt.rs
index b8e59e4420f3..6bfd91cfa1f4 100644
--- a/rust/kernel/mm/virt.rs
+++ b/rust/kernel/mm/virt.rs
@@ -123,9 +123,7 @@ pub fn zap_page_range_single(&self, address: usize, size: usize) {
         // SAFETY: By the type invariants, the caller has read access to this VMA, which is
         // sufficient for this method call. This method has no requirements on the vma flags. The
         // address range is checked to be within the vma.
-        unsafe {
-            bindings::zap_page_range_single(self.as_ptr(), address, size)
-        };
+        unsafe { bindings::zap_page_range_single(self.as_ptr(), address, size) };
     }
 
     /// If the [`VM_MIXEDMAP`] flag is set, returns a [`VmaMixedMap`] to this VMA, otherwise
-- 
2.43.0



> with the above changed:
> 
> Acked-by: Alice Ryhl <aliceryhl at google.com> # Rust and Binder

Thanks!

-- 
Cheers,

David