From: Byungchul Park <byungchul.park@lge.com>
To: "Paul E. McKenney" <paulmck@linux.ibm.com>
Cc: Joel Fernandes <joel@joelfernandes.org>,
josh@joshtriplett.org, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@lge.com
Subject: Re: [PATCH v2] rcu: Change return type of rcu_spawn_one_boost_kthread()
Date: Mon, 1 Jul 2019 09:01:14 +0900 [thread overview]
Message-ID: <20190701000114.GB23795@X58A-UD3R> (raw)
In-Reply-To: <20190630193834.GU26519@linux.ibm.com>
On Sun, Jun 30, 2019 at 12:38:34PM -0700, Paul E. McKenney wrote:
> On Fri, Jun 28, 2019 at 11:43:39AM +0900, Byungchul Park wrote:
> > On Thu, Jun 27, 2019 at 01:57:03PM -0700, Paul E. McKenney wrote:
> > > On Thu, Jun 27, 2019 at 09:42:40AM -0400, Joel Fernandes wrote:
> > > > On Thu, Jun 27, 2019 at 04:07:46PM +0900, Byungchul Park wrote:
> > > > > Hello,
> > > > >
> > > > > I tested if the WARN_ON_ONCE() is fired with my box and it was ok.
> > > >
> > > > Looks pretty safe to me and nice clean up!
> > > >
> > > > Acked-by: Joel Fernandes (Google) <joel@joelfernandes.org>
> > >
> > > Agreed, but I still cannot find where this applies. I did try rcu/next,
> > > which is currently here:
> > >
> > > commit b989ff070574ad8b8621d866de0a8e9a65d42c80 (rcu/rcu/next, rcu/next)
> > > Merge: 4289ee7d5a83 11ca7a9d541d
> > > Author: Paul E. McKenney <paulmck@linux.ibm.com>
> > > Date: Mon Jun 24 09:12:39 2019 -0700
> > >
> > > Merge LKMM and RCU commits
> > >
> > > Help?
> >
> > commit 204d7a60670f3f6399a4d0826667ab7863b3e429
> >
> > Merge LKMM and RCU commits
> >
> > I made it on top of the above. And could you tell me which branch I'd
> > better use when developing. I think it's been changing sometimes.
>
> That would be because idiot here took so much care to avoid risking
> pushing some early development commits into the upcoming merge window
> that he managed to misplace them entirely. The -rcu tree's "dev" branch
> now includes them. Could you please port to it?
Of course, I can.
> a1af11a24cb0 ("rcu/nocb: Make __call_rcu_nocb_wake() safe for many callbacks")
>
> > Thank you for the answer in advance!
>
> And please accept my apologies for the very confusing tree layout this
> time around!
It would be totally OK if you give me the answer when I feel confused
with branch for development. :)
>
> Thanx, Paul
prev parent reply other threads:[~2019-07-01 0:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 7:07 [PATCH v2] rcu: Change return type of rcu_spawn_one_boost_kthread() Byungchul Park
2019-06-27 13:42 ` Joel Fernandes
2019-06-27 20:57 ` Paul E. McKenney
2019-06-28 2:43 ` Byungchul Park
2019-06-30 19:38 ` Paul E. McKenney
2019-07-01 0:01 ` Byungchul Park [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=20190701000114.GB23795@X58A-UD3R \
--to=byungchul.park@lge.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.ibm.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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