From fda82e044f089a1e61464f73ea677c990545033e Mon Sep 17 00:00:00 2001
From: Sebastian Fricke <sebastian.fricke.linux@gmail.com>
Date: Thu, 23 Jul 2020 06:23:00 +0200
Subject: [PATCH] Try to fix buggy code sections #4

---
 _posts/2020-07-09-eudyptula-challenge-Part-5.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/_posts/2020-07-09-eudyptula-challenge-Part-5.md b/_posts/2020-07-09-eudyptula-challenge-Part-5.md
index e648f831d5d10..3fb1334a00a68 100644
--- a/_posts/2020-07-09-eudyptula-challenge-Part-5.md
+++ b/_posts/2020-07-09-eudyptula-challenge-Part-5.md
@@ -118,16 +118,20 @@ Configure and allocate the device:
         ...
 
 Enable & address the device and get a device descriptor within:  
+
     ...
     status = hub_port_init(hub, udev, port1, i);
     ...
+
 Register the device and find a driver:  
+
         ...
         status = usb_new_device(udev);
         ...
     }
 
 Within `usb_alloc_dev` a device slot is acquired by calling the host controller function `xhci_alloc_dev`:
+
     int xhci_alloc_dev(struct usb_hcd *hcd, struct usb_device *udev)
     {
         ...
@@ -152,6 +156,7 @@ Those data structures are for example:
 
 
 In `hub_port_init`, the hub driver makes calls to the host controller driver to enable the device and get an address for the device:  
+
     static int
     hub_port_init(struct usb_hub *hub, struct usb_device *udev, int port1,
             int retry_counter)
@@ -169,6 +174,7 @@ In `hub_port_init`, the hub driver makes calls to the host controller driver to
 When the device is addressed, the default control endpoint (ep0) is activated, which enables the system to get access to the device's configuration, status, and control information.
 
 Within `usb_new_device`, a call to `device_add` includes the device into `sysfs` and finally executes `kobject_uevent`:  
+
     int device_add(struct device *dev)
     {
         ...