Fix itemize indentation

Remove extra spaces before \item under \begin{itemize} to normalize
indentation. This change is formatting-only and does not alter any text
content. Normalized style reduces unnecessary diff noise and improves
consistency across the document.

Co-authored-by: EricccTaiwan <[email protected]>
Signed-off-by: Chia-Hao Chiu <[email protected]>

Author: Jordymalone

lkmpg.tex

@@ -1109,7 +1109,7 @@ \subsection{Unregistering A Device}
 You should not use this counter directly, but there are functions defined in \src{include/linux/module.h} which let you display this counter:
 
 \begin{itemize}
-  \item \cpp|module_refcount(THIS_MODULE)|: Return the value of reference count of current module.
+\item \cpp|module_refcount(THIS_MODULE)|: Return the value of reference count of current module.
 \end{itemize}
 
 Note: The use of \cpp|try_module_get(THIS_MODULE)| and \cpp|module_put(THIS_MODULE)| within a module's own code is considered unsafe and should be avoided.
@@ -1296,8 +1296,8 @@ \subsection{Manage /proc file with seq\_file}
 If you want more information, you can read this web page:
 
 \begin{itemize}
-  \item \url{https://lwn.net/Articles/22355/}
-  \item \url{https://kernelnewbies.org/Documents/SeqFileHowTo}
+\item \url{https://lwn.net/Articles/22355/}
+\item \url{https://kernelnewbies.org/Documents/SeqFileHowTo}
 \end{itemize}
 
 You can also read the code of \src{fs/seq\_file.c} in the Linux kernel.
@@ -1561,12 +1561,12 @@ \section{System Calls}
 For more information, check out the following:
 
 \begin{itemize}
- \item \href{https://lwn.net/Articles/804849/}{Cook: Security things in Linux v5.3}
- \item \href{https://lwn.net/Articles/12211/}{Unexporting the system call table}
- \item \href{https://lwn.net/Articles/810077/}{Control-flow integrity for the kernel}
- \item \href{https://lwn.net/Articles/813350/}{Unexporting kallsyms\_lookup\_name()}
- \item \href{https://www.kernel.org/doc/Documentation/kprobes.txt}{Kernel Probes (Kprobes)}
- \item \href{https://lwn.net/Articles/569635/}{Kernel address space layout randomization}
+\item \href{https://lwn.net/Articles/804849/}{Cook: Security things in Linux v5.3}
+\item \href{https://lwn.net/Articles/12211/}{Unexporting the system call table}
+\item \href{https://lwn.net/Articles/810077/}{Control-flow integrity for the kernel}
+\item \href{https://lwn.net/Articles/813350/}{Unexporting kallsyms\_lookup\_name()}
+\item \href{https://www.kernel.org/doc/Documentation/kprobes.txt}{Kernel Probes (Kprobes)}
+\item \href{https://lwn.net/Articles/569635/}{Kernel address space layout randomization}
 \end{itemize}
 
 The source code here is an example of such a kernel module.
@@ -1782,10 +1782,10 @@ \subsection{Spinlocks}
 Unlike \cpp|spin_lock_irq()| and \cpp|spin_lock_irqsave()|, which disable both hardware and software interrupts, \cpp|spin_lock_bh()| is useful when hardware interrupts need to remain active.
 
 For more information about spinlock usage and lock types, see the following resources:
- \begin{itemize}
-  \item \href{https://www.kernel.org/doc/Documentation/locking/spinlocks.txt}{Lesson 1: Spin locks}
-  \item\href{https://docs.kernel.org/locking/locktypes.html}{Lock types and their rules}
- \end{itemize}
+\begin{itemize}
+\item \href{https://www.kernel.org/doc/Documentation/locking/spinlocks.txt}{Lesson 1: Spin locks}
+\item\href{https://docs.kernel.org/locking/locktypes.html}{Lock types and their rules}
+\end{itemize}
 
 \subsection{Read and write locks}
 \label{sec:rwlock}
@@ -1809,9 +1809,9 @@ \subsection{Atomic operations}
 But there are some problems, such as the memory model of the kernel doesn't match the model formed by the C11 atomics.
 For further details, see:
 \begin{itemize}
- \item \href{https://www.kernel.org/doc/Documentation/atomic_t.txt}{kernel documentation of atomic types}
- \item \href{https://lwn.net/Articles/691128/}{Time to move to C11 atomics?}
- \item \href{https://lwn.net/Articles/698315/}{Atomic usage patterns in the kernel}
+\item \href{https://www.kernel.org/doc/Documentation/atomic_t.txt}{kernel documentation of atomic types}
+\item \href{https://lwn.net/Articles/691128/}{Time to move to C11 atomics?}
+\item \href{https://lwn.net/Articles/698315/}{Atomic usage patterns in the kernel}
 \end{itemize}
 
 % FIXME: we should rewrite this section
@@ -1917,8 +1917,8 @@ \subsection{GPIO}
 When using GPIO, you must set it as either output with \cpp|gpio_direction_output()| or input with \cpp|gpio_direction_input()|.
 
 \begin{itemize}
-  \item when the GPIO is set as output, you can use \cpp|gpio_set_value()| to choose to set it to high voltage or low voltage.
-  \item when the GPIO is set as input, you can use \cpp|gpio_get_value()| to read whether the voltage is high or low.
+\item when the GPIO is set as output, you can use \cpp|gpio_set_value()| to choose to set it to high voltage or low voltage.
+\item when the GPIO is set as input, you can use \cpp|gpio_get_value()| to read whether the voltage is high or low.
 \end{itemize}
 
 \subsection{Control the LED's on/off state}
@@ -2170,9 +2170,9 @@ \section{Virtual Input Device Driver}
 The driver needs to export a \cpp|vinput_device()| that contains the virtual device name and \cpp|vinput_ops| structure that describes:
 
 \begin{itemize}
-    \item the init function: \cpp|init()|
-    \item the input event injection function: \cpp|send()|
-    \item the readback function: \cpp|read()|
+\item the init function: \cpp|init()|
+\item the input event injection function: \cpp|send()|
+\item the readback function: \cpp|read()|
 \end{itemize}
 
 Then using \cpp|vinput_register_device()| and \cpp|vinput_unregister_device()| will add a new device to the list of support virtual input devices.