diff options
| author | Paul E. McKenney <paulmck@kernel.org> | 2023-11-13 08:52:19 -0800 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@kernel.org> | 2023-11-20 10:51:23 -0800 |
| commit | 7bc1be926374ea53085b443af4132fc78fde1418 (patch) | |
| tree | 602053f51f3f0ecb11be987ebe91c0595e3da809 | |
| parent | 55d3ffa2a0adf7f381a51cb808f72f51caa7e463 (diff) | |
| download | perfbook-7bc1be926374ea53085b443af4132fc78fde1418.tar.gz | |
howto: Clarify "copy-pasta" idiom
Reported-by: ma jun <yztaoj@outlook.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
| -rw-r--r-- | howto/howto.tex | 21 |
1 files changed, 12 insertions, 9 deletions
diff --git a/howto/howto.tex b/howto/howto.tex index 58b472e8..55270cba 100644 --- a/howto/howto.tex +++ b/howto/howto.tex @@ -276,15 +276,18 @@ require that you practice producing code. This ability might in turn permit you to: \begin{enumerate} - \item See what the kernel does so that you can check to see - if a proposed use case is valid. - \item Chase down a kernel bug. - \item Use information in the kernel to more easily chase down - a userspace bug. - \item Produce a fix for a kernel bug. - \item Create a straightforward kernel feature, whether from - scratch or using the modern copy-pasta development - methodology. + \item See what the concurrent code does so that you can check + to see if a proposed use case is valid. + \item Chase down a bug in concurrent code. + \item Use information in the concurrent code base to more + easily chase down a bug in other code interacting with + that code base. + \item Produce a fix for a bug in concurrent code. + \item Create a straightforward feature in a concurrent code + base, whether coding by hand from scratch or using the + modern ``copy-pasta'' development methodology involving + downloading code from Internet.\footnote{ + But be careful of copyright and licensing issues!} \end{enumerate} If you are proficient with straightforward uses of locks and |