From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Bristot de Oliveira <bristot@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Clark Williams <williams@redhat.com>,
"Luis Claudio R . Goncalves" <lgoncalv@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] sched/rt: disable RT_RUNTIME_SHARE by default and document it
Date: Tue, 15 Nov 2016 10:27:04 -0500 [thread overview]
Message-ID: <20161115102704.2260b143@gandalf.local.home> (raw)
In-Reply-To: <cover.1479204252.git.bristot@redhat.com>
On Tue, 15 Nov 2016 11:39:09 +0100
Daniel Bristot de Oliveira <bristot@redhat.com> wrote:
> Disable RT_RUNTIME_SHARE by default and document it.
>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Clark Williams <williams@redhat.com>
> Cc: Luis Claudio R. Goncalves <lgoncalv@redhat.com>
> Cc: linux-kernel@vger.kernel.org
>
> Daniel Bristot de Oliveira (2):
> sched/rt: Disable RT_RUNTIME_SHARE by default
> sched/rt: Document RT_RUNTIME_SHARE sched feature
>
> kernel/sched/features.h | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
I don't see why this is two patches. A change and a comment can go
together, and probably should, especially since the comment explains
the change as well.
With a folded patch...
Acked-by: Steven Rostedt <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2016-11-15 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 10:39 [PATCH 0/2] sched/rt: disable RT_RUNTIME_SHARE by default and document it Daniel Bristot de Oliveira
2016-11-15 10:39 ` [PATCH 1/2] sched/rt: Disable RT_RUNTIME_SHARE by default Daniel Bristot de Oliveira
2016-11-15 10:39 ` [PATCH 2/2] sched/rt: Document RT_RUNTIME_SHARE sched feature Daniel Bristot de Oliveira
2016-11-15 13:01 ` [PATCH 0/2] sched/rt: disable RT_RUNTIME_SHARE by default and document it Luis Claudio R. Goncalves
2016-11-15 15:27 ` Steven Rostedt [this message]
2016-11-15 16:57 ` Daniel Bristot de Oliveira
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=20161115102704.2260b143@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bristot@redhat.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=williams@redhat.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;
as well as URLs for NNTP newsgroup(s).