From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Gang Li <ligang.bdlg@bytedance.com>,
Peter Zijlstra <peterz@infradead.org>,
John Hubbard <jhubbard@nvidia.com>, Mel Gorman <mgorman@suse.de>
Cc: linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>, Ingo Molnar <mingo@redhat.com>,
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>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>
Subject: Re: [PATCH v6 0/2] sched/numa: add per-process numa_balancing
Date: Fri, 28 Apr 2023 14:40:24 +0700 [thread overview]
Message-ID: <76534699-e270-b450-c18e-f7c35c325bcf@gmail.com> (raw)
In-Reply-To: <9ba3577b-0098-86da-ff2e-636cb5a8ae1a@bytedance.com>
On 4/27/23 12:17, Gang Li wrote:
> Hi,
>
> Looks like there are no objections or comments. Do you have any ideas?
>
> Can we merge this patch in the next merge window.
>
We're at 6.4 merge window, so the maintainer focus is to send PR updates
to Linus. And this series didn't get applied before this merge window.
Wait until 6.4-rc1 is out and reroll.
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-04-28 7:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 14:06 [PATCH v6 0/2] sched/numa: add per-process numa_balancing Gang Li
2023-04-12 14:10 ` [PATCH v6 1/2] sched/numa: use static_branch_inc/dec for sched_numa_balancing Gang Li
2023-04-12 14:11 ` [PATCH v6 2/2] sched/numa: add per-process numa_balancing Gang Li
2023-04-27 5:17 ` [PATCH v6 0/2] " Gang Li
2023-04-28 7:40 ` Bagas Sanjaya [this message]
2023-04-28 7:45 ` Gang Li
2023-05-17 9:28 ` Gang Li
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=76534699-e270-b450-c18e-f7c35c325bcf@gmail.com \
--to=bagasdotme@gmail.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=jhubbard@nvidia.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=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).