From: "Paul E. McKenney" <paulmck@kernel.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Josh Triplett <josh@joshtriplett.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, Li Zefan <lizefan@huawei.com>
Subject: Re: [PATCH 0/4] RFC: support for global CPU list abbreviations
Date: Sun, 8 Nov 2020 13:24:29 -0800 [thread overview]
Message-ID: <20201108212429.GA8195@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <ca462940-c81d-d968-c870-e1a991331522@windriver.com>
On Sun, Nov 08, 2020 at 03:21:40PM -0500, Paul Gortmaker wrote:
> On 2020-11-08 1:02 p.m., Paul E. McKenney wrote:
>
> > Or I can carry them if you wish. My expected changes in response to
> > this series are shown below, and are also what I used to test it.
>
> Thanks Paul - that would get linux-next exposure w/o me pestering sfr.
> If nobody else has objections, having them in rcu-next would be great.
Unless/until someone objects, you got it!
Thanx, Paul
prev parent reply other threads:[~2020-11-08 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 16:08 [PATCH 0/4] RFC: support for global CPU list abbreviations Paul Gortmaker
2020-11-08 16:08 ` [PATCH 1/4] cpumask: un-inline cpulist_parse; prepare for ascii helpers Paul Gortmaker
2020-11-08 16:08 ` [PATCH 2/4] cpumask: make "all" alias global and not just RCU Paul Gortmaker
2020-11-08 16:08 ` [PATCH 3/4] cpumask: add a "none" alias to complement "all" Paul Gortmaker
2020-11-08 16:08 ` [PATCH 4/4] cpumask: add "last" alias for cpu list specifications Paul Gortmaker
2020-11-08 18:02 ` [PATCH 0/4] RFC: support for global CPU list abbreviations Paul E. McKenney
2020-11-08 20:21 ` Paul Gortmaker
2020-11-08 21:24 ` Paul E. McKenney [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=20201108212429.GA8195@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tglx@linutronix.de \
/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).