From: Michael Kerrisk <mtk.manpages@googlemail.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Why does timerfd() only support CLOCK_REALTIME and CLOCK_MONOTONIC?
Date: Mon, 9 Feb 2009 10:29:51 +1300 [thread overview]
Message-ID: <cfd18e0f0902081329j4b18c4f2g91269d3209f1932d@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0902081245560.18839@alien.or.mcafeemobile.com>
> @@ -186,12 +187,9 @@ SYSCALL_DEFINE2(timerfd_create, int, clo
> BUILD_BUG_ON(TFD_CLOEXEC != O_CLOEXEC);
> BUILD_BUG_ON(TFD_NONBLOCK != O_NONBLOCK);
>
> - if (flags & ~(TFD_CLOEXEC | TFD_NONBLOCK))
> + if ((flags & ~TFD_FLAGS_SET) ||
> + invalid_clockid(clockid))
> return -EINVAL;
Oh! Does this mean that in 2.6.2[789] it wasn't possible to use
TFD_TIMER_ABSTIME?
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
next prev parent reply other threads:[~2009-02-08 21:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 18:25 Michael Kerrisk
2009-02-08 19:29 ` Davide Libenzi
2009-02-08 20:46 ` Davide Libenzi
2009-02-08 21:18 ` Michael Kerrisk
2009-02-08 21:22 ` Davide Libenzi
2009-02-08 21:26 ` Michael Kerrisk
2009-02-08 21:29 ` Michael Kerrisk [this message]
2009-02-08 21:50 ` Davide Libenzi
2009-02-08 21:53 ` Michael Kerrisk
2009-02-08 22:06 ` Davide Libenzi
2009-02-08 22:10 ` [stable] " Greg KH
2009-02-08 22:27 ` Michael Kerrisk
2009-02-08 22:12 ` Michael Kerrisk
2009-02-09 2:24 ` Greg KH
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=cfd18e0f0902081329j4b18c4f2g91269d3209f1932d@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=tglx@linutronix.de \
/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®