From: "H. Peter Anvin" <hpa@zytor.com>
To: Alexey Dobriyan <adobriyan@openvz.org>
Cc: akpm@osdl.org, devel@openvz.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] lutimesat: actual syscall and wire-up on i386
Date: Sat, 27 Jan 2007 23:59:55 -0800 [thread overview]
Message-ID: <45BC57FB.4010209@zytor.com> (raw)
In-Reply-To: <20070126112345.GC11128@localhost.sw.ru>
Alexey Dobriyan wrote:
> +asmlinkage long sys_lutimesat(int dfd, char __user *filename, struct timeval __user *utimes)
Could we get these to take struct timespec instead of struct timeval?
Right now we have a real problem in that the interfaces that *set* times
take struct timeval (microsecond granularity) but the interfaces that
*get* times return struct timespec (nanosecond granularity), which means
information loss on any setting operations.
-hpa
next prev parent reply other threads:[~2007-01-28 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 11:23 [PATCH 3/3] lutimesat: actual syscall and wire-up on i386 Alexey Dobriyan
2007-01-26 20:39 ` Andrew Morton
2007-01-26 20:45 ` Ulrich Drepper
2007-01-29 11:05 ` Alexey Dobriyan
2007-01-29 15:07 ` Ulrich Drepper
2007-01-29 16:02 ` Alexey Dobriyan
2007-01-28 7:59 ` H. Peter Anvin [this message]
2007-01-29 9:58 ` Alexey Dobriyan
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=45BC57FB.4010209@zytor.com \
--to=hpa@zytor.com \
--cc=adobriyan@openvz.org \
--cc=akpm@osdl.org \
--cc=devel@openvz.org \
--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