Merge pull request #306 from EricccTaiwan/fix

Clarify tasklet limitations and deprecation plans

Author: jserv

lkmpg.tex

@@ -1279,7 +1279,7 @@ \subsection{Manage /proc file with seq\_file}
   \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.
+You can also read the code of \src{fs/seq\_file.c} in the Linux kernel.
 
 \section{sysfs: Interacting with your module}
 \label{sec:sysfs}
@@ -1921,7 +1921,7 @@ \subsection{Tasklets}
 Example tasklet init continues...
 Example tasklet ends
 \end{verbatim}
-Although tasklet is easy to use, it comes with several drawbacks, and developers are discussing about getting rid of tasklet in linux kernel.
+Although tasklet is easy to use, it comes with several drawbacks, and developers have been discussing their removal from the Linux kernel.
 The tasklet callback runs in atomic context, inside a software interrupt, meaning that it cannot sleep or access user-space data, so not all work can be done in a tasklet handler.
 Also, the kernel only allows one instance of any given tasklet to be running at any given time; multiple different tasklet callbacks can run in parallel.