From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>, Mel Gorman <mgorman@suse.de>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v8 1/4] sched/numa: drop sysctl_numa_balancing_settle_count sysctl
Date: Mon, 16 Dec 2013 07:58:04 +0800 [thread overview]
Message-ID: <52ae4216.67ed440a.577e.ffff88e8SMTPIN_ADDED_BROKEN@mx.google.com> (raw)
In-Reply-To: <20131215165643.GC16438@laptop.programming.kicks-ass.net>
On Sun, Dec 15, 2013 at 05:56:43PM +0100, Peter Zijlstra wrote:
>On Sun, Dec 15, 2013 at 04:41:10PM +0800, Wanpeng Li wrote:
>> Do you mean something like:
>>
>> commit 887c290e (sched/numa: Decide whether to favour task or group
>> weights
>> based on swap candidate relationships) drop the check against
>> sysctl_numa_balancing_settle_count, this patch remove the sysctl.
>>
>> Acked-by: Mel Gorman <mgorman@suse.de>
>> Reviewed-by: Rik van Riel <riel@redhat.com>
>> Acked-by: David Rientjes <rientjes@google.com>
>> Signed-off-by: Wanpeng Li <liwanp@linux.vnet.ibm.com>
>> ---
>> Changelog:
>> v7 -> v8:
>> * remove references to it in Documentation/sysctl/kernel.txt
>> ---
>
>No need to insert another --- line, just the one below the SoB,
>
>> Documentation/sysctl/kernel.txt | 5 -----
>> include/linux/sched/sysctl.h | 1 -
>> kernel/sched/fair.c | 9 ---------
>> kernel/sysctl.c | 7 -------
>> 4 files changed, 0 insertions(+), 22 deletions(-)
>
>Everything between --- and the patch proper (usually started with an
>Index line or other diff syntax thingy), including this diffstat you
>have, will be made to disappear.
>
>But yes indeed. The Changelog should describe the patch as is, and the
>differences between this and the previous version are relevant only to
>the reviewer who saw the previous version too. But once we commit the
>patch, the previous version ceases to exist (in the commit history) and
>therefore such comments loose their intrinsic meaning and should go away
>too.
Thanks for your great explanation. ;-)
Regards,
Wanpeng Li
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2013-12-15 23:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 7:23 Wanpeng Li
2013-12-12 7:23 ` [PATCH v8 2/4] sched/numa: use wrapper function task_node to get node which task is on Wanpeng Li
2013-12-12 7:23 ` [PATCH v8 3/4] sched/numa: use wrapper function task_faults_idx to calculate index in group_faults Wanpeng Li
2013-12-12 7:23 ` [PATCH v8 4/4] sched/numa: fix period_slot recalculation Wanpeng Li
2013-12-13 18:09 ` [PATCH v8 1/4] sched/numa: drop sysctl_numa_balancing_settle_count sysctl Peter Zijlstra
2013-12-15 8:41 ` Wanpeng Li
[not found] ` <20131215084110.GA4316@hacker.(null)>
2013-12-15 16:56 ` Peter Zijlstra
2013-12-15 23:58 ` Wanpeng Li [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=52ae4216.67ed440a.577e.ffff88e8SMTPIN_ADDED_BROKEN@mx.google.com \
--to=liwanp@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=peterz@infradead.org \
--cc=riel@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