mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: <ligang.bdlg@bytedance.com>
Cc: <linux-api@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	John Hubbard <jhubbard@nvidia.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	"Valentin Schneider" <vschneid@redhat.com>,
	<linux-fsdevel@vger.kernel.org>, <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v5 0/2] sched/numa: add per-process numa_balancing
Date: Wed, 16 Nov 2022 12:45:40 -0800	[thread overview]
Message-ID: <20221116204540.163222-1-jhubbard@nvidia.com> (raw)
In-Reply-To: <20221027025302.45766-1-ligang.bdlg@bytedance.com>

Hi Gang Li,

If you want this to move forward, you'll likely need to include the
original To: and Cc: people. And also, any new ones who responded with
review comments. I've added here, those that I found in your v4 series
[1].

The message that I'm replying to appears to only be sent to a couple of
generic lists, and so it's going to be invisible to most of those
people.

Also, I already acked this series separately [2], before I saw the
missing Cc's.

[1] https://lore.kernel.org/all/20220929064359.46932-1-ligang.bdlg@bytedance.com/

[2] https://lore.kernel.org/all/49ed07b1-e167-7f94-9986-8e86fb60bb09@nvidia.com/

thanks,
-- 
John Hubbard
NVIDIA

      parent reply	other threads:[~2022-11-16 20:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27  2:53 Gang Li
2022-10-27  2:53 ` [PATCH v5 1/2] sched/numa: use static_branch_inc/dec for sched_numa_balancing Gang Li
2022-10-27  2:53 ` [PATCH v5 2/2] sched/numa: add per-process numa_balancing Gang Li
2022-11-10  3:11 ` [PATCH v5 0/2] " John Hubbard
2022-11-16 20:45 ` John Hubbard [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=20221116204540.163222-1-jhubbard@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=ligang.bdlg@bytedance.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@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
all inboxes | Powered by JetHome®