public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Randy.Dunlap" <rddunlap@osdl.org>
Subject: Re: [PATCH ] POSIX clocks & timers take 15 (NOT HIGH RES)
Date: Thu, 05 Dec 2002 12:09:40 -0800	[thread overview]
Message-ID: <3DEFB284.A209E75C@mvista.com> (raw)
In-Reply-To: Pine.LNX.4.44.0212050904390.27298-100000@home.transmeta.com

Linus Torvalds wrote:
> 
> Ok, finally starting to look at merging this, however:
> 
> This must go (we already have a timespec, there's no way it should be
> here in <asm/signal.h>):
> 
>         +#ifndef _STRUCT_TIMESPEC
>         +#define _STRUCT_TIMESPEC
>         +struct timespec {
>         +       time_t  tv_sec;         /* seconds */
>         +       long    tv_nsec;        /* nanoseconds */
>         +};
>         +#endif /* _STRUCT_TIMESPEC */

OK.
> 
> and you have things like
> 
>         +       if ((flags & TIMER_ABSTIME) &&
>         +           (clock->clock_get != do_posix_clock_monotonic_gettime)) {
>         +       }else{
>         +       }

A hang over from the high res code, I will remove the empty
else.
> 
> and
> 
>         +if (!p) {
>         +printk("in sub_remove for id=%d called with null pointer.\n", id);
>         +return(0);
>         +}

That is in there!?  I will check into and fix it.
> 
> and obviously the "nanosleep()" thing and the CLOCK_NANOSLEEP_ENTRY()
> stuff has been discussed in the unrelated thread (ie it doesn't work for
> alpha or other architectures).

Right!  I am merging this now.

I think something went into bk5 yesterday that will require
an update.  I will update to 2.5.50-bk5 with the above fixes
and sent it ... soon.
-- 
George Anzinger   george@mvista.com
High-res-timers: 
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml

  parent reply	other threads:[~2002-12-05 20:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05  7:20 [PATCH ] POSIX clocks & timers take 15 (NOT HIGH RES) george anzinger
2002-12-05 17:13 ` Linus Torvalds
2002-12-05 18:35   ` Randy.Dunlap
2002-12-05 20:09   ` george anzinger [this message]
2002-12-06  9:23   ` george anzinger
2002-12-08  7:45   ` [PATCH ] POSIX clocks & timers take 16 " george anzinger
2002-12-20  9:52   ` [PATCH ] POSIX clocks & timers take 17 " george anzinger
2002-12-20 19:47   ` [PATCH ] POSIX clocks & timers take 17.1 " george anzinger
2002-12-30 23:49   ` [PATCH ] POSIX clocks & timers take 18 " george anzinger
2003-01-04  0:26   ` [PATCH ] POSIX clocks & timers take 19 " george anzinger
2003-01-04  0:42   ` [PATCH ] POSIX clocks & timers take 19.1 " george anzinger
2003-01-08 23:11   ` [PATCH ] POSIX clocks & timers take 20 " george anzinger
  -- strict thread matches above, loose matches on Subject: below --
2002-11-28  0:42 [PATCH ] POSIX clocks & timers take 15 " george anzinger

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=3DEFB284.A209E75C@mvista.com \
    --to=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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