public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel Fernandes <joel@joelfernandes.org>
To: "Paul E. McKenney" <paulmck@linux.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Josh Triplett <josh@joshtriplett.org>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	linux-kselftest <linux-kselftest@vger.kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Shuah Khan <shuah@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] rcutorture: Select from only online CPUs
Date: Tue, 26 Mar 2019 19:48:55 -0400	[thread overview]
Message-ID: <20190326234855.GA108868@google.com> (raw)
In-Reply-To: <20190326204613.GS4102@linux.ibm.com>

On Tue, Mar 26, 2019 at 01:46:13PM -0700, Paul E. McKenney wrote:
[snip]
> > Any way, I will just add back CPU0 forcefully to the cpus list in my testing,
> > without checking for the online file existence, and see what happens :-) If
> > there's no smoke, then I'll roll that into a patch and send it out.
> 
> Sounds good, especially if you include a few of the uniprocessor tests.  ;-)

Yes, I will do those as well. Thanks for the reminder :-). Let us wait on
merging until then, then. I will reply back here about the uni processor
testing tomorrow.

thanks,

 - Joel


      reply	other threads:[~2019-03-26 23:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-23  3:46 [PATCH] rcutorture: Select from only online CPUs Joel Fernandes (Google)
2019-03-25 15:01 ` Paul E. McKenney
2019-03-25 16:33   ` Joel Fernandes
2019-03-25 16:42     ` Paul E. McKenney
2019-03-25 22:02       ` Joel Fernandes
2019-03-25 22:40       ` Joel Fernandes
2019-03-26 16:01         ` Paul E. McKenney
2019-03-26 18:35           ` Joel Fernandes
2019-03-26 18:40             ` Joel Fernandes
2019-03-26 20:46               ` Paul E. McKenney
2019-03-26 23:48                 ` Joel Fernandes [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=20190326234855.GA108868@google.com \
    --to=joel@joelfernandes.org \
    --cc=jiangshanlai@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=paulmck@linux.ibm.com \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    /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