From: 王贇 <yun.wang@linux.alibaba.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Juri Lelli" <juri.lelli@redhat.com>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Dietmar Eggemann" <dietmar.eggemann@arm.com>,
"Ben Segall" <bsegall@google.com>, "Mel Gorman" <mgorman@suse.de>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Kees Cook" <keescook@chromium.org>,
"Iurii Zaikin" <yzaikin@google.com>,
"Michal Koutný" <mkoutny@suse.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.ibm.com>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Jonathan Corbet" <corbet@lwn.net>
Subject: Re: [PATCH v8 0/2] sched/numa: introduce numa locality
Date: Fri, 7 Feb 2020 10:31:14 +0800 [thread overview]
Message-ID: <c721b898-4826-9073-e80e-0730dcc18ecf@linux.alibaba.com> (raw)
In-Reply-To: <20200206202504.7175c4a8@oasis.local.home>
On 2020/2/7 上午9:25, Steven Rostedt wrote:
> On Fri, 7 Feb 2020 09:10:33 +0800
> 王贇 <yun.wang@linux.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.
Aha, I do believe that's the situation...
I'll resend the v8 with the Ack from Randy, thanks for the advice :-)
Regards,
Michael Wang
>
> -- Steve
>
next prev parent reply other threads:[~2020-02-07 2:31 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 3:43 [PATCH 0/3] sched/numa: introduce advanced numa statistic 王贇
2019-11-13 3:44 ` [PATCH 1/3] sched/numa: advanced per-cgroup " 王贇
2019-11-13 3:45 ` [PATCH 2/3] sched/numa: expose per-task pages-migration-failure 王贇
2019-11-13 3:45 ` [PATCH 3/3] sched/numa: documentation for per-cgroup numa stat 王贇
2019-11-13 15:09 ` Jonathan Corbet
2019-11-14 1:52 ` 王贇
2019-11-13 18:28 ` Iurii Zaikin
2019-11-14 2:22 ` 王贇
2019-11-15 2:29 ` [PATCH v2 " 王贇
2019-11-20 9:45 ` [PATCH 0/3] sched/numa: introduce advanced numa statistic 王贇
2019-11-25 1:35 ` 王贇
2019-11-27 1:48 ` [PATCH v2 " 王贇
2019-11-27 1:49 ` [PATCH v2 1/3] sched/numa: advanced per-cgroup " 王贇
2019-11-27 10:19 ` Mel Gorman
2019-11-28 2:09 ` 王贇
2019-11-28 12:39 ` Michal Koutný
2019-11-28 13:41 ` 王贇
2019-11-28 15:58 ` Michal Koutný
2019-11-29 1:52 ` 王贇
2019-11-29 5:19 ` 王贇
2019-11-29 10:06 ` Michal Koutný
2019-12-02 2:11 ` 王贇
2019-11-27 1:50 ` [PATCH v2 2/3] sched/numa: expose per-task pages-migration-failure 王贇
2019-11-27 10:00 ` Mel Gorman
2019-12-02 2:22 ` 王贇
2019-11-27 1:50 ` [PATCH v2 3/3] sched/numa: documentation for per-cgroup numa stat 王贇
2019-11-27 4:58 ` Randy Dunlap
2019-11-27 5:54 ` 王贇
2019-12-03 5:59 ` [PATCH v3 0/2] sched/numa: introduce numa locality 王贇
2019-12-03 6:00 ` [PATCH v3 1/2] sched/numa: introduce per-cgroup NUMA locality info 王贇
2019-12-04 2:33 ` Randy Dunlap
2019-12-04 2:38 ` 王贇
2019-12-03 6:02 ` [PATCH v3 2/2] sched/numa: documentation for per-cgroup numa statistics 王贇
2019-12-03 13:43 ` Jonathan Corbet
2019-12-04 2:27 ` 王贇
2019-12-04 7:58 ` [PATCH v4 0/2] sched/numa: introduce numa locality 王贇
2019-12-04 7:59 ` [PATCH v4 1/2] sched/numa: introduce per-cgroup NUMA locality info 王贇
2019-12-05 3:28 ` Randy Dunlap
2019-12-05 3:29 ` Randy Dunlap
2019-12-05 3:52 ` 王贇
2019-12-04 8:00 ` [PATCH v4 2/2] sched/numa: documentation for per-cgroup numa statistics 王贇
2019-12-05 3:40 ` Randy Dunlap
2019-12-05 6:53 ` [PATCH v5 0/2] sched/numa: introduce numa locality 王贇
2019-12-05 6:53 ` [PATCH v5 1/2] sched/numa: introduce per-cgroup NUMA locality info 王贇
2019-12-05 6:54 ` [PATCH v5 2/2] sched/numa: documentation for per-cgroup numa, statistics 王贇
2019-12-10 2:19 ` [PATCH v5 0/2] sched/numa: introduce numa locality 王贇
2019-12-13 1:43 ` [PATCH v6 " 王贇
2019-12-13 1:47 ` [PATCH v6 1/2] sched/numa: introduce per-cgroup NUMA locality info 王贇
2020-01-03 15:14 ` Michal Koutný
2020-01-04 4:51 ` 王贇
2019-12-13 1:48 ` [PATCH v6 2/2] sched/numa: documentation for per-cgroup numa 王贇
2019-12-27 2:22 ` [PATCH v6 0/2] sched/numa: introduce numa locality 王贇
2020-01-17 2:19 ` 王贇
2020-01-19 6:08 ` [PATCH v7 " 王贇
2020-01-19 6:09 ` [PATCH v7 1/2] sched/numa: introduce per-cgroup NUMA locality info 王贇
2020-01-19 6:09 ` [PATCH v7 2/2] sched/numa: documentation for per-cgroup numa, statistics 王贇
2020-01-21 0:12 ` Randy Dunlap
2020-01-21 1:58 ` 王贇
2020-01-21 1:56 ` [PATCH v8 0/2] sched/numa: introduce numa locality 王贇
2020-01-21 1:57 ` [PATCH v8 1/2] sched/numa: introduce per-cgroup NUMA locality info 王贇
2020-01-21 1:57 ` [PATCH v8 2/2] sched/numa: documentation for per-cgroup numa, statistics 王贇
2020-01-21 2:08 ` Randy Dunlap
2020-02-07 1:10 ` [PATCH v8 0/2] sched/numa: introduce numa locality 王贇
2020-02-07 1:25 ` Steven Rostedt
2020-02-07 2:31 ` 王贇 [this message]
2020-02-07 2:37 ` [PATCH RESEND " 王贇
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=c721b898-4826-9073-e80e-0730dcc18ecf@linux.alibaba.com \
--to=yun.wang@linux.alibaba.com \
--cc=bsegall@google.com \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=mkoutny@suse.com \
--cc=paulmck@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=yzaikin@google.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).