From: Pavel Rabel <pavel@web.sajt.cz>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] timer.h obsolete comments
Date: Wed, 13 Dec 2000 00:01:07 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.21.0012122343180.26198-100000@web.sajt.cz> (raw)
Hi Linus,
Are the old static timers gone completely?
Some comments are either obsolete or out of place.
Pavel Rabel
--- include/linux/timer.h.old Tue Dec 12 22:07:35 2000
+++ include/linux/timer.h Tue Dec 12 22:09:28 2000
@@ -5,13 +5,9 @@
#include <linux/list.h>
/*
- * This is completely separate from the above, and is the
+ * Old-style "hardcoded" timers are gone, this is the
* "new and improved" way of handling timers more dynamically.
* Hopefully efficient and general enough for most things.
- *
- * The "hardcoded" timers above are still useful for well-
- * defined problems, but the timer-list is probably better
- * when you need multiple outstanding timers or similar.
*
* The "data" field is in case you want to use the same
* timeout function for several timeouts. You can use this
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-12-12 23:34 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=Pine.LNX.4.21.0012122343180.26198-100000@web.sajt.cz \
--to=pavel@web.sajt.cz \
--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;
as well as URLs for NNTP newsgroup(s).