Ran cargo fmt, clippy fixes, suppressed some warns

I will start working on stack traces tonight and tomorrow.

We need to be able to 'unwind' by finding calling functions.

kernel/src/arch/x86_64/drivers/framebuffer/display.rs

@@ -10,17 +10,19 @@ use core::panic;
 use limine::framebuffer::Framebuffer;
 use spin::{Lazy, Mutex};
 
-pub static FRAMEBUFFER_WRITER: Lazy<Mutex<Option<FramebufferWriter>>> = Lazy::new(|| {
-    Mutex::new(FRAMEBUFFER_REQUEST.get_response().map_or_else(
-        || {
-            panic!("Framebuffer request failed");
-        },
-        |framebuffer_response| {
-            let framebuffer = framebuffer_response.framebuffers().next().unwrap();
-            Some(FramebufferWriter::new(framebuffer))
-        },
-    ))
-});
+pub static FRAMEBUFFER_WRITER: Lazy<Mutex<Option<FramebufferWriter>>> =
+    Lazy::new(|| {
+        Mutex::new(FRAMEBUFFER_REQUEST.get_response().map_or_else(
+            || {
+                panic!("Framebuffer request failed");
+            },
+            |framebuffer_response| {
+                let framebuffer =
+                    framebuffer_response.framebuffers().next().unwrap();
+                Some(FramebufferWriter::new(framebuffer))
+            },
+        ))
+    });
 
 /// The updated writer stores necessary fields from the [Framebuffer].
 /// This ensures that the contained types are Send, as Framebuffer was
@@ -28,7 +30,8 @@ pub static FRAMEBUFFER_WRITER: Lazy<Mutex<Option<FramebufferWriter>>> = Lazy::ne
 ///
 /// It also avoids the requirement for lifetimes.
 ///
-/// Note this does not implement Writer as these functions only handle drawing pixels.
+/// Note this does not implement Writer as these functions only handle drawing
+/// pixels.
 pub struct FramebufferWriter {
     pitch: u64,
     bpp: u16,