From: Andrew Morton <akpm@digeo.com>
To: george anzinger <george@mvista.com>
Cc: linux-kernel@vger.kernel.org, Eric.Piel@Bull.Net
Subject: Re: [PATCH] Some clean up of the time code.
Date: Tue, 10 Jun 2003 11:25:41 -0700 [thread overview]
Message-ID: <20030610112541.3f12586d.akpm@digeo.com> (raw)
In-Reply-To: <3EE5FB06.1060207@mvista.com>
george anzinger <george@mvista.com> wrote:
>
> Andrew Morton wrote:
> > george anzinger <george@mvista.com> wrote:
> >
> >>-void do_settimeofday(struct timeval *tv)
> >> +int do_settimeofday(struct timespec *tv)
> >> {
> >> + if ((unsigned long)tv->tv_nsec > NSEC_PER_SEC)
> >> + return -EINVAL;
> >> +
> >
> >
> > Should that be ">="?
> >
> > Is there any reasonable way to avoid breaking existing
> > do_settimeofday() implementations? That's just more grief all round.
>
> Hm. Giving this more thought, the main reason for the change was to
> move to the timespec from the timeval, i.e. nanoseconds instead of
> microseconds. The error check was put in because the function was
> already being changed. The reason to move to the timespec is to
> complete the change made to xtime and to more correctly align with the
> POSIX clock_settime, both of which use timespec.
>
Well if it's really the Right Thing To Do then OK. Was just checking.
About 30 do_settimeofday() implementations need to be repaired.
next prev parent reply other threads:[~2003-06-10 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 0:56 george anzinger
2003-06-10 1:22 ` Andrew Morton
2003-06-10 5:43 ` george anzinger
2003-06-10 15:36 ` george anzinger
2003-06-10 18:25 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-09 22:57 george anzinger
2003-06-09 23:36 ` john stultz
2003-05-23 22:49 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=20030610112541.3f12586d.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=Eric.Piel@Bull.Net \
--cc=george@mvista.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
all inboxes | Powered by JetHome®