From: Rusty Trivial Russell <rusty@rustcorp.com.au>
To: torvalds@transmeta.com, akpm@zip.com.au, linux-kernel@vger.kernel.org
Subject: [TRIVIAL] Remove reference to timer_exit() from kernel-locking.tmpl, fix typo.
Date: Fri, 06 Dec 2002 14:45:32 +1100 [thread overview]
Message-ID: <20021206035756.3D6C92C2E0@lists.samba.org> (raw)
From: Tommi Virtanen <tv@debian.org>
timer_exit() isn't a public function, and doesn't even exist in 2.5.
2.4 calls it internally after timers. It seems timer users need not
do anything special.
--- trivial-2.5-bk/Documentation/DocBook/kernel-locking.tmpl.orig 2002-12-06 13:56:55.000000000 +1100
+++ trivial-2.5-bk/Documentation/DocBook/kernel-locking.tmpl 2002-12-06 13:56:55.000000000 +1100
@@ -1055,10 +1055,8 @@
Another common problem is deleting timers which restart
themselves (by calling <function>add_timer()</function> at the end
of their timer function). Because this is a fairly common case
- which is prone to races, you can put a call to
- <function>timer_exit()</function> at the very end of your timer function,
- and user <function>del_timer_sync()</function>
- (<filename class=headerfile>include/linux/timer.h</filename>)
+ which is prone to races, you should use <function>del_timer_sync()</function>
+ (<filename class=headerfile>include/linux/timer.h</filename>)
to handle this case. It returns the number of times the timer
had to be deleted before we finally stopped it from adding itself back
in.
--
Don't blame me: the Monkey is driving
File: Tommi Virtanen <tv@debian.org>: Remove reference to timer_exit() from kernel-locking.tmpl, fix typo.
reply other threads:[~2002-12-06 3:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021206035756.3D6C92C2E0@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®