[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180209070006.ndi57j2llrywo4yt@gmail.com>
Date: Fri, 9 Feb 2018 08:00:06 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Frederic Weisbecker <frederic@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Chris Metcalf <cmetcalf@...lanox.com>,
Thomas Gleixner <tglx@...utronix.de>,
Luiz Capitulino <lcapitulino@...hat.com>,
Christoph Lameter <cl@...ux.com>,
"Paul E . McKenney" <paulmck@...ux.vnet.ibm.com>,
Wanpeng Li <kernellwp@...il.com>,
Mike Galbraith <efault@....de>, Rik van Riel <riel@...hat.com>
Subject: Re: [PATCH 0/6] isolation: 1Hz residual tick offloading v5
* Frederic Weisbecker <frederic@...nel.org> wrote:
> sched/isolation: Residual 1Hz scheduler tick offload
> sched/isolation: Tick offload documentation
Please try to start each title with a verb.
[ ... and preferably not by prepending 'do' ;-) ]
Beyond making changelogs more consistent, this will actually also add real
information to the title, because, for example, any of these possible variants:
sched/isolation: Fix tick offload documentation
sched/isolation: Update tick offload documentation
sched/isolation: Add tick offload documentation
sched/isolation: Remove tick offload documentation
sched/isolation: Fix residual 1Hz scheduler tick offload
sched/isolation: Update residual 1Hz scheduler tick offload
sched/isolation: Introduce residual 1Hz scheduler tick offload
sched/isolation: Remove residual 1Hz scheduler tick offload
will tell us _a lot more_ about the nature of the changes from the shortlog alone!
Thanks,
Ingo
Powered by blists - more mailing lists