kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nish Aravamudan <nish.aravamudan@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] Status of TODO item jiffies towards end
Date: Thu, 21 Apr 2005 16:13:08 +0000	[thread overview]
Message-ID: <29495f1d050421091379f3cae1@mail.gmail.com> (raw)

On 4/21/05, blm@woodheap.org <blm@woodheap.org> wrote:
> I am new at this but am very keen to contribute.  I
> thought I would start at the end of the TODO on the
> web site (hoping noone else thought of the same thing)
> and see what happens.
> 
> The item:
> 
> Some drivers do:
> 
>         if ((jiffies - data->last_updated > HZ * 2) ||
>             (jiffies < data->last_updated))
> 
> Should be:
> 
>         #include <linux/jiffies.h>
>         if (time_after(jiffies, data->last_updated + HZ * 2))
> 
> Have a patch for drivers/i2c/chips/*.
> 
> It seems this has been fixed because I only found the
> problem code in drivers/i2c/chips/* in kernel source 2.6.10.

Yes, many of these have been fixed. Marcelo Parisi has been posting a
number of patches to KJML recently (check archives).

> Are there any items that need attention that it is known that
> noone is working on?  What kernel tree should I be looking at?

I'm not sure there is any way to verify this without asking about
specific TODO entries. As far as a tree to base on, it's always
whatever current mainline is (2.6.12-rc3 currently).

Thanks,
Nish

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

             reply	other threads:[~2005-04-21 16:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 16:13 Nish Aravamudan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-21 10:48 [KJ] Status of TODO item jiffies towards end blm

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=29495f1d050421091379f3cae1@mail.gmail.com \
    --to=nish.aravamudan@gmail.com \
    --cc=kernel-janitors@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;
as well as URLs for NNTP newsgroup(s).