public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@o2.pl>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: Dmitry Adamushko <dmitry.adamushko@gmail.com>,
	Ingo Molnar <mingo@elte.hu>, Nick Piggin <npiggin@suse.de>,
	"Siddha\, Suresh B" <suresh.b.siddha@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: Rationalize sys_sched_rr_get_interval()
Date: Tue, 16 Oct 2007 11:42:52 +0200	[thread overview]
Message-ID: <20071016094252.GD1000@ff.dom.local> (raw)
In-Reply-To: <471410EF.90808@bigpond.net.au>

On 16-10-2007 03:16, Peter Williams wrote:
...
> 
> I'd suggest that we modify sched_rr_get_interval() to return -EINVAL 
> (with *interval set to zero) if the target task is not SCHED_RR.  That 
> way we can save a lot of unnecessary code.  I'll work on a patch.
...

I like this idea! But, since this a system call maybe at least
something like RFC would be nicer...

>>
>> Sorry for too harsh words.
> 
> I didn't consider them harsh.

So, I can't be mistaken for a rapper yet? I'll work on it...

Cheers,
Jarek P.

PS: Peter, for some unknown reason I don't receive your messages.
If you get back some errors from my side I'd be interested to see
it (alternative: jarkao2 at gmail.com).

  reply	other threads:[~2007-10-16  9:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11  0:37 [PATCH] sched: Rationalize sys_sched_rr_get_interval() Peter Williams
2007-10-11  6:59 ` Ingo Molnar
2007-10-11  7:44   ` Dmitry Adamushko
2007-10-11 22:23     ` Peter Williams
2007-10-12  6:49       ` Jarek Poplawski
2007-10-13  1:29         ` Peter Williams
2007-10-15 11:11           ` Jarek Poplawski
2007-10-16  1:16             ` Peter Williams
2007-10-16  9:42               ` Jarek Poplawski [this message]
2007-10-17  0:23                 ` Peter Williams
2007-10-12  6:59       ` Ingo Molnar

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=20071016094252.GD1000@ff.dom.local \
    --to=jarkao2@o2.pl \
    --cc=dmitry.adamushko@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=npiggin@suse.de \
    --cc=pwil3058@bigpond.net.au \
    --cc=suresh.b.siddha@intel.com \
    /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