From: Johannes Weiner <hannes@saeurebad.de>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] add time_now_after and other macros which compare with jiffies
Date: Sat, 08 Mar 2008 17:12:00 +0100 [thread overview]
Message-ID: <877igd6vqn.fsf@saeurebad.de> (raw)
In-Reply-To: <200803080735.06984.hidave.darkstar@gmail.com> (Dave Young's message of "Sat, 8 Mar 2008 07:35:06 +0800")
Hi Dave, Andrew and all
Dave Young <hidave.darkstar@gmail.com> writes:
> +/* time_now_after(a) return true if now (jiffies) is after a */
> +#define time_now_after(a) time_after(jiffies, a)
> +
> +/* time_now_before(a) return true if now (jiffies) is before a */
> +#define time_now_before(a) time_before(jiffies, a)
> +
> +/* time_now_after_eq(a) return true if now (jiffies) is after or equal to a */
> +#define time_now_after_eq(a) time_after_eq(jiffies, a)
> +
> +/* time_now_before_eq(a) return true if now (jiffies) is before or equal to a */
> +#define time_now_before_eq(a) time_before_eq(jiffies, a)
How about even more obvious names like time_is_past(), time_is_future(),
...?
Sorry, I missed v1. Should have proposed that earlier.
Hannes
next prev parent reply other threads:[~2008-03-08 16:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 23:35 [PATCH v2] add time_now_after and other macros which compare with jiffies Dave Young
2008-03-08 16:12 ` Johannes Weiner [this message]
2008-03-09 0:54 ` Dave Young
2008-03-09 9:58 ` Alan Cox
2008-03-09 10:44 ` Dave Young
2008-03-09 11:08 ` Alan Cox
2008-03-09 19:01 ` Andrew Morton
2008-03-09 20:06 ` Alan Cox
2008-03-10 2:03 ` Dave Young
2008-03-10 2:41 ` Johannes Weiner
2008-03-09 18:36 ` Andrew Morton
2008-03-09 20:03 ` Alan Cox
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=877igd6vqn.fsf@saeurebad.de \
--to=hannes@saeurebad.de \
--cc=akpm@linux-foundation.org \
--cc=hidave.darkstar@gmail.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.