linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: mingo@redhat.com, peterz@infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: Question on comment header for for_each_domain()
Date: Wed, 7 Nov 2018 15:00:02 -0800	[thread overview]
Message-ID: <20181107230002.GA15577@linux.ibm.com> (raw)

Hello!

The header comment for for_each_domain() talks about a call to
synchronize_sched() within detach_destroy_domains(), but I am not
seeing any such call.  Because synchronize_sched() is now folded into
synchronize_rcu(), I have a patch that edits the comment, but it looks
like a larger change is needed.

Or am I blind today?

							Thanx, Paul


             reply	other threads:[~2018-11-07 23:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 23:00 Paul E. McKenney [this message]
2018-11-08  9:21 ` Question on comment header for for_each_domain() Peter Zijlstra
2018-11-08 15:31   ` Paul E. McKenney
2018-11-08 15:35     ` Peter Zijlstra
2018-11-08 16:11       ` Paul E. McKenney

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=20181107230002.GA15577@linux.ibm.com \
    --to=paulmck@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).