[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200206202504.7175c4a8@oasis.local.home>
Date: Thu, 6 Feb 2020 20:25:04 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: 王贇 <yun.wang@...ux.alibaba.com>
Cc: Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Juri Lelli <juri.lelli@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Luis Chamberlain <mcgrof@...nel.org>,
Kees Cook <keescook@...omium.org>,
Iurii Zaikin <yzaikin@...gle.com>,
Michal Koutný <mkoutny@...e.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org,
"Paul E. McKenney" <paulmck@...ux.ibm.com>,
Randy Dunlap <rdunlap@...radead.org>,
Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH v8 0/2] sched/numa: introduce numa locality
On Fri, 7 Feb 2020 09:10:33 +0800
王贇 <yun.wang@...ux.alibaba.com> wrote:
> Hi, Peter, Ingo
>
> Could you give some comments please?
A little word of advice. When sending new versions of a patch. Don't
send them as a reply to the previous version. Some developers (and I
believe Peter is one of them), wont look for new patches in threads,
and this may never be seen by him.
New versions of patches (v8 in this case) need to start a new thread
and be at the top level. It's hard to manage patches when a thread
series in embedded in another thread series.
-- Steve
Powered by blists - more mailing lists