From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Miklos Szeredi" <miklos@szeredi.hu>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
hch@lst.de, viro@zeniv.linux.org.uk, jamie@shareable.org,
drepper@redhat.com, linux-fsdevel@vger.kernel.org,
subrata@linux.vnet.ibm.com
Subject: Re: [parch 1/4] vfs: utimensat(): ignore tv_sec if tv_nsec == UTIME_OMIT or UTIME_NOW
Date: Wed, 4 Jun 2008 14:01:48 +0200 [thread overview]
Message-ID: <cfd18e0f0806040501i43f4faeagd44599efea0463c6@mail.gmail.com> (raw)
In-Reply-To: <E1K3kbK-0007c4-PF@pomaz-ex.szeredi.hu>
On Wed, Jun 4, 2008 at 6:27 AM, Miklos Szeredi <miklos@szeredi.hu> wrote:
>> The POSIX.1 draft spec for utimensat() says that if a times[n].tv_nsec
>> field is UTIME_OMIT or UTIME_NOW, then the value in the corresponding
>> tv_sec field is ignored. However the current Linux implementation
>> requires the tv_sec value to be zero (or the EINVAL error results).
>> This requirement should be removed.
>>
>> CC: Miklos Szeredi <miklos@szeredi.hu>
>> CC: Al Viro <viro@zeniv.linux.org.uk>
>> CC: Ulrich Drepper <drepper@redhat.com>
>> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
>
> Would it be possible to quote the relevant parts of the draft?
Will do, for the next revision of this patch series.
> Otherwise
>
> Acked-by: Miklos Szeredi <mszeredi@suse.cz>
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
prev parent reply other threads:[~2008-06-04 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 22:24 [parch 1/4] vfs: utimensat(): ignore tv_sec if tv_nsec == UTIME_OMIT or UTIME_NOW Michael Kerrisk
2008-06-04 4:27 ` Miklos Szeredi
2008-06-04 12:01 ` Michael Kerrisk [this message]
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=cfd18e0f0806040501i43f4faeagd44599efea0463c6@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=hch@lst.de \
--cc=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=subrata@linux.vnet.ibm.com \
--cc=viro@zeniv.linux.org.uk \
/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).