From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Chris Metcalf <cmetcalf@mellanox.com>,
Thomas Gleixner <tglx@linutronix.de>,
Luiz Capitulino <lcapitulino@redhat.com>,
Christoph Lameter <cl@linux.com>,
"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>,
Wanpeng Li <kernellwp@gmail.com>, Mike Galbraith <efault@gmx.de>,
Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH 0/6] isolation: 1Hz residual tick offloading v6
Date: Fri, 16 Feb 2018 14:38:58 +0100 [thread overview]
Message-ID: <20180216133858.GD25201@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1518655694-8057-1-git-send-email-frederic@kernel.org>
On Thu, Feb 15, 2018 at 01:48:08AM +0100, Frederic Weisbecker wrote:
> The version addresses the reviews from Ingo on v5:
>
> * Start changelog titles with verbs.
> * Improve/reword several comments.
> * Improve/reword documentation.
> * Various cosmetic changes.
> * Use BUG_ON() on boot allocation failure.
>
Thanks!
prev parent reply other threads:[~2018-02-16 13:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 0:48 Frederic Weisbecker
2018-02-15 0:48 ` [PATCH 1/6] sched: Rename init_rq_hrtick to hrtick_rq_init Frederic Weisbecker
2018-02-17 10:22 ` Thomas Gleixner
2018-02-15 0:48 ` [PATCH 2/6] nohz: Allow to check if remote CPU tick is stopped Frederic Weisbecker
2018-02-17 10:27 ` Thomas Gleixner
2018-02-15 0:48 ` [PATCH 3/6] sched/isolation: Isolate workqueues when "nohz_full=" is set Frederic Weisbecker
2018-02-17 10:31 ` Thomas Gleixner
2018-02-15 0:48 ` [PATCH 4/6] sched/isolation: Offload residual 1Hz scheduler tick Frederic Weisbecker
2018-02-17 10:50 ` Thomas Gleixner
2018-02-20 15:44 ` Frederic Weisbecker
2018-02-15 0:48 ` [PATCH 5/6] sched/nohz: Remove the 1 Hz tick code Frederic Weisbecker
2018-02-17 10:51 ` Thomas Gleixner
2018-02-15 0:48 ` [PATCH 6/6] sched/isolation: Update nohz documentation to explain tick offload Frederic Weisbecker
2018-02-17 10:53 ` Thomas Gleixner
2018-02-20 16:40 ` Frederic Weisbecker
2018-02-16 13:38 ` Peter Zijlstra [this message]
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=20180216133858.GD25201@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=cl@linux.com \
--cc=cmetcalf@mellanox.com \
--cc=efault@gmx.de \
--cc=frederic@kernel.org \
--cc=kernellwp@gmail.com \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=riel@redhat.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
Powered by JetHome