The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Dave Young" <hidave.darkstar@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] add time_after_now and other macros which compare with jiffies
Date: Fri, 7 Mar 2008 01:22:44 -0800	[thread overview]
Message-ID: <20080307012244.ed7625ec.akpm@linux-foundation.org> (raw)
In-Reply-To: <a8e1da0803070112p6a5e076aw569a50a69de91504@mail.gmail.com>

On Fri, 7 Mar 2008 17:12:29 +0800 "Dave Young" <hidave.darkstar@gmail.com> wrote:

> Indeed, I will add proper comment before them.

Sob.  Of the 809 usages of time_after(), it appears that over 700 are
comparing with jiffies.  So with your (good) change, someone will get
buried in well-meaning convert-to-time_after_now patches.

I wonder who that might be?

  reply	other threads:[~2008-03-07  9:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07  3:09 [PATCH RFC] add time_after_now and other macros which compare with jiffies Dave Young
2008-03-07  9:02 ` Andrew Morton
2008-03-07  9:12   ` Dave Young
2008-03-07  9:22     ` Andrew Morton [this message]
2008-03-07  9:36       ` Dave Young

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=20080307012244.ed7625ec.akpm@linux-foundation.org \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox