From: SeongJae Park <sj38.park@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: perfbook@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 2/2] toolsoftrade: Add suffix `()` to function name
Date: Wed, 4 Jan 2017 03:59:53 +0900 [thread overview]
Message-ID: <20170103185953.3000-2-sj38.park@gmail.com> (raw)
In-Reply-To: <20170103185953.3000-1-sj38.park@gmail.com>
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
toolsoftrade/toolsoftrade.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/toolsoftrade/toolsoftrade.tex b/toolsoftrade/toolsoftrade.tex
index 899ef01e6e2a..bc51437eb141 100644
--- a/toolsoftrade/toolsoftrade.tex
+++ b/toolsoftrade/toolsoftrade.tex
@@ -1383,7 +1383,7 @@ initialization code.
The Linux kernel uses
\co{struct task_struct} pointers to track kthreads,
-\co{kthread_create} to create them,
+\co{kthread_create()} to create them,
\co{kthread_should_stop()} to externally suggest that they stop
(which has no POSIX equivalent),
\co{kthread_stop()} to wait for them to stop, and
--
2.10.0
next prev parent reply other threads:[~2017-01-03 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 18:59 [PATCH 1/2] toolsoftrade: Close uncompleted parentheses SeongJae Park
2017-01-03 18:59 ` SeongJae Park [this message]
2017-01-03 19:32 ` [PATCH 2/2] toolsoftrade: Add suffix `()` to function name Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170103185953.3000-2-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=perfbook@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox