Skip to content

Commit

Permalink
Merge pull request #262 from jouae/master
Browse files Browse the repository at this point in the history
Modify the descritions of seq_file and flowchart
  • Loading branch information
jserv authored Jul 2, 2024
2 parents 1d3943a + 7a6dd1f commit 031b9d2
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions lkmpg.tex
Original file line number Diff line number Diff line change
Expand Up @@ -1234,7 +1234,7 @@ \subsection{Manage /proc file with seq\_file}
The \cpp|seq_file| API starts a sequence when a user read the \verb|/proc| file.

A sequence begins with the call of the function \cpp|start()|.
If the return is a non \cpp|NULL| value, the function \cpp|next()| is called.
If the return is a non \cpp|NULL| value, the function \cpp|next()| is called; otherwise, otherwise, the \cpp|stop()| function is called directly.
This function is an iterator, the goal is to go through all the data.
Each time \cpp|next()| is called, the function \cpp|show()| is also called.
It writes data values in the buffer read by the user.
Expand All @@ -1251,13 +1251,12 @@ \subsection{Manage /proc file with seq\_file}
\begin{tikzpicture}[node distance=2cm, thick]
\node (start) [startstop] {start() treatment};
\node (branch1) [decision, below of=start, yshift=-1cm] {return is NULL?};
\node (emptynode) [right of=branch1, xshift=2cm] {Yes};
\node (next) [process, below of=branch1, yshift=-1cm] {next() treatment};
\node (branch2) [decision, below of=next, yshift=-1cm] {return is NULL?};
\node (stop) [startstop, below of=branch2, yshift=-1cm] {stop() treatment};

\draw [->] (start) -- (branch1);
\draw [->] (branch1) -- node[anchor=east] {} (emptynode);
\draw [->] (branch1.east) to [out=135, in=-135, bend left=45] node [right] {Yes} (stop.east);
\draw [->] (branch1) -- node[left=2em, anchor=south] {No} (next);
\draw [->] (next) -- (branch2);
\draw [->] (branch2.west) to [out=135, in=-135, bend left=45] node [left] {No} (next.west);
Expand Down

0 comments on commit 031b9d2

Please sign in to comment.