From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Paul Turner <pjt@google.com>
Cc: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH tip] sched/trivial: Remove cfs bandwidth period check in tg_set_cfs_period()
Date: Tue, 13 Dec 2011 13:53:14 +0100 [thread overview]
Message-ID: <1323780794.9082.16.camel@twins> (raw)
In-Reply-To: <CAPM31RKR8dvtSmMmV7xO5FnBgY62=fQugXYANNGYMOiAE6iQbg@mail.gmail.com>
On Tue, 2011-12-13 at 04:40 -0800, Paul Turner wrote:
>
> It's OK though since period is always strictly unsigned so any -ve
> becomes larger than the max allowed period and it spits out -EINVAL as
> appropriate.
>
> So Kamelesh's patch above is good as is.
>
> Acked-by: Paul Turner <pjt@google.com>
Right you are, thanks!
next prev parent reply other threads:[~2011-12-13 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 13:59 [PATCH tip] sched/trivial: Remove cfs bandwidth period check in tg_set_cfs_period() Kamalesh Babulal
2011-12-12 13:05 ` Peter Zijlstra
2011-12-13 12:40 ` Paul Turner
2011-12-13 12:53 ` Peter Zijlstra [this message]
2011-12-21 11:43 ` [tip:sched/core] sched: " tip-bot for Kamalesh Babulal
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=1323780794.9082.16.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pjt@google.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