mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
	drepper@redhat.com, clameter@sgi.com
Subject: Re: [PATCH] CPU time clock support in clock_* syscalls
Date: Mon, 4 Oct 2004 22:27:18 -0700	[thread overview]
Message-ID: <200410050527.i955RIwt004128@magilla.sf.frob.com> (raw)
In-Reply-To: Andrew Morton's message of  Monday, 4 October 2004 22:20:59 -0700 <20041004222059.5e9ca9f6.akpm@osdl.org>

> This will always return an error.

Yes, indeed.  It's just picky about which one.  Something I meant to
mention: I do not allow clock_settime on CPU timers, because I don't know
of any worthwhile reason to want to support it.  You get EINVAL or EFAULT
if your arguments are bogus, and EPERM if they are valid.  This is the
POSIX-compliant error code choice.


Thanks,
Roland

  reply	other threads:[~2004-10-05  5:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05  5:15 Roland McGrath
2004-10-05  5:20 ` Andrew Morton
2004-10-05  5:27   ` Roland McGrath [this message]
2004-10-05  6:43 ` Nick Piggin
2004-10-05 18:28   ` Roland McGrath
2004-10-05 23:18     ` Nick Piggin
2004-10-06  0:33       ` Roland McGrath
2004-10-06  0:51         ` Nick Piggin
2004-10-05 15:39 ` Christoph Lameter
2004-10-05 18:38   ` Roland McGrath
2004-10-05 20:53     ` Christoph Lameter
2004-10-05 21:22       ` Roland McGrath
2004-10-05 21:28         ` Christoph Lameter
2004-10-06  0:35           ` Roland McGrath
2004-10-06  1:21             ` Christoph Lameter
2004-10-07 19:45               ` Roland McGrath
2004-10-07 20:24                 ` Christoph Lameter
2004-10-05 17:29 ` Christoph Lameter

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=200410050527.i955RIwt004128@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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®